Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aafe9fa33b393c3dcf4d8d80ff5783c3483c8e1f970ead4848288f4878103724

Tx prefix hash: 1a7c6ef4316d0aed425ef2b2c3f824ab6cc285bf6a8607d270bf181b7abebe8f
Tx public key: 1cc2774ea74b9f0fe3fa3f17b74e88fee0028c4b48f3ee0fe83ee5e5df640d89
Timestamp: 1581086753 Timestamp [UTC]: 2020-02-07 14:45:53 Age [y:d:h:m:s]: 06:094:03:39:36
Block: 60374 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1470888 RingCT/type: yes/0
Extra: 011cc2774ea74b9f0fe3fa3f17b74e88fee0028c4b48f3ee0fe83ee5e5df640d890211000000017adf42d3000000000000000000

1 output(s) for total of 0.387219030575 xmr

stealth address amount amount idx tag
00: 3a7a6a3a342e9559ee4008d9852662515b791874df6eeb3430b24776751753a8 0.387219030575 111292 of 0 -

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": 60384, "vin": [ { "gen": { "height": 60374 } } ], "vout": [ { "amount": 387219030575, "target": { "key": "3a7a6a3a342e9559ee4008d9852662515b791874df6eeb3430b24776751753a8" } } ], "extra": [ 1, 28, 194, 119, 78, 167, 75, 159, 15, 227, 250, 63, 23, 183, 78, 136, 254, 224, 2, 140, 75, 72, 243, 238, 15, 232, 62, 229, 229, 223, 100, 13, 137, 2, 17, 0, 0, 0, 1, 122, 223, 66, 211, 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: