Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a72bc7b0b5a7261f3b910a1918a2f6c9f5c49ef4dd1076a31cddd8b4bd63e673

Tx prefix hash: 04ddc0c4a271b25ad568b6f0b35731dc9f2da004019e5c3847e16538b8087eb1
Tx public key: 12b18c33489c430beb8cf1069226ce70bf3d477e3d398e1f2173be9b85f906d3
Timestamp: 1731443613 Timestamp [UTC]: 2024-11-12 20:33:33 Age [y:d:h:m:s]: 01:178:08:16:50
Block: 1152328 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 378523 RingCT/type: yes/0
Extra: 0112b18c33489c430beb8cf1069226ce70bf3d477e3d398e1f2173be9b85f906d3021100000003007f978a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: fcb0dcf65b6392e05c9c82faad18194a4f0b835dd200b875474eb595f8bd6ff0 0.000600000000 1637923 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": 1152338, "vin": [ { "gen": { "height": 1152328 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fcb0dcf65b6392e05c9c82faad18194a4f0b835dd200b875474eb595f8bd6ff0" } } ], "extra": [ 1, 18, 177, 140, 51, 72, 156, 67, 11, 235, 140, 241, 6, 146, 38, 206, 112, 191, 61, 71, 126, 61, 57, 142, 31, 33, 115, 190, 155, 133, 249, 6, 211, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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: