Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5d0ad7f435927c8c18dfd76737dc2a0452f2d87142ccd0fb20fbdffe53e7546e

Tx prefix hash: 9eee44527737c074ac17f30b78374b5e8a789f5081ddd61b11bb18cd3a681a6c
Tx public key: 65246c47b85a4e9f871cb52aa722b3a46d5e10ad6daa6d90a4b160c816f95f20
Timestamp: 1772487831 Timestamp [UTC]: 2026-03-02 21:43:51 Age [y:d:h:m:s]: 00:256:23:29:09
Block: 1489336 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 189068 RingCT/type: yes/0
Extra: 0165246c47b85a4e9f871cb52aa722b3a46d5e10ad6daa6d90a4b160c816f95f20021100000004f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 0b0265cd339ebbf108d17f2239165de96ab1de1343ae6bcd74c0d14054b659e9 0.000600000000 1978826 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": 1489346, "vin": [ { "gen": { "height": 1489336 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0b0265cd339ebbf108d17f2239165de96ab1de1343ae6bcd74c0d14054b659e9" } } ], "extra": [ 1, 101, 36, 108, 71, 184, 90, 78, 159, 135, 28, 181, 42, 167, 34, 179, 164, 109, 94, 16, 173, 109, 170, 109, 144, 164, 177, 96, 200, 22, 249, 95, 32, 2, 17, 0, 0, 0, 4, 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: