Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e4c014081797e64fd9051fd4b3980c62ecd633833eced1983c1893beefa2f4ef

Tx prefix hash: 666f89d41cae081e1fdff40dca7ca740116f292ae1d026c1eb6ebd109befde0b
Tx public key: 9998ddc3efc517de05bf9cbc9f4d8bd0287c11cfa2a425d9071dd5f35b3a142f
Timestamp: 1582931008 Timestamp [UTC]: 2020-02-28 23:03:28 Age [y:d:h:m:s]: 06:074:23:29:28
Block: 73669 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1458732 RingCT/type: yes/0
Extra: 019998ddc3efc517de05bf9cbc9f4d8bd0287c11cfa2a425d9071dd5f35b3a142f0211000000248a2ee0d9000000000000000000

1 output(s) for total of 0.349868482049 xmr

stealth address amount amount idx tag
00: 8c3ffc512ba2f27da4be7edbd1b8cbdfb388be10d12d28e5b048d298a774d206 0.349868482049 135940 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": 73679, "vin": [ { "gen": { "height": 73669 } } ], "vout": [ { "amount": 349868482049, "target": { "key": "8c3ffc512ba2f27da4be7edbd1b8cbdfb388be10d12d28e5b048d298a774d206" } } ], "extra": [ 1, 153, 152, 221, 195, 239, 197, 23, 222, 5, 191, 156, 188, 159, 77, 139, 208, 40, 124, 17, 207, 162, 164, 37, 217, 7, 29, 213, 243, 91, 58, 20, 47, 2, 17, 0, 0, 0, 36, 138, 46, 224, 217, 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: