Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c867c435753db6e1fdb5771a0e1553d48ee27f66f36902fb4ca5d1ed7235fee1

Tx prefix hash: 5c6133d03c241e0c4c216a421229a1f514260c81b3cf0b2652a955b287a0231e
Tx public key: e1e8e64a342fb4757f72d1ee9f4952bc56594f4e72da868668abb5c4e89f885a
Timestamp: 1722444334 Timestamp [UCT]: 2024-07-31 16:45:34 Age [y:d:h:m:s]: 00:296:08:08:51
Block: 1077817 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 211736 RingCT/type: yes/0
Extra: 01e1e8e64a342fb4757f72d1ee9f4952bc56594f4e72da868668abb5c4e89f885a02110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 21a7f813d77e5087c7ecf0666f1c88c534479d142f47278e055409a604efebc7 0.600000000000 1550372 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 dinasty-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": 1077827, "vin": [ { "gen": { "height": 1077817 } } ], "vout": [ { "amount": 600000000, "target": { "key": "21a7f813d77e5087c7ecf0666f1c88c534479d142f47278e055409a604efebc7" } } ], "extra": [ 1, 225, 232, 230, 74, 52, 47, 180, 117, 127, 114, 209, 238, 159, 73, 82, 188, 86, 89, 79, 78, 114, 218, 134, 134, 104, 171, 181, 196, 232, 159, 136, 90, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8