Dinastycoin Explorer Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: d2f01b3e11987f5241167806e66b52b63017bc6a6c866bcd0013dc2440d6bebc

Tx prefix hash: 11d591e130dd4d6d673fde57a6704c6916c2faf8796fd174e9800ef908966f66
Tx public key: d21f33d2461ad099ddecd67dfc1d90af113a0c0ec676541af847680c1ac74817
Timestamp: 1771610665 Timestamp [UTC]: 2026-02-20 18:04:25 Age [y:d:h:m:s]: 00:269:19:30:49
Block: 1482082 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 198324 RingCT/type: yes/0
Extra: 01d21f33d2461ad099ddecd67dfc1d90af113a0c0ec676541af847680c1ac74817021100000006f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 7fda4e5b1ff5a5f18883d8c2bb69a2978268c090249dd090aff4f78794e99b0b 0.000600000000 1971470 of 15 -

Check which outputs belong to given dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinastycoin-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1482092, "vin": [ { "gen": { "height": 1482082 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7fda4e5b1ff5a5f18883d8c2bb69a2978268c090249dd090aff4f78794e99b0b" } } ], "extra": [ 1, 210, 31, 51, 210, 70, 26, 208, 153, 221, 236, 214, 125, 252, 29, 144, 175, 17, 58, 12, 14, 198, 118, 84, 26, 248, 71, 104, 12, 26, 199, 72, 23, 2, 17, 0, 0, 0, 6, 241, 136, 200, 168, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: