Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ff0c0f38b7a1eddf3bb393ba4a8e4fba54b12cfdc03c3bd26a5e57e0cf62fe94

Tx prefix hash: ddab2ffd9a61084c32426c475b7d1fc89ed3fad9508daa756c52a4f7e54d9d44
Tx public key: d01ecbe0ac331cb45a40db7402f85974dc9c98e8f7e37116588de662dd15134d
Timestamp: 1719930794 Timestamp [UCT]: 2024-07-02 14:33:14 Age [y:d:h:m:s]: 00:277:10:36:18
Block: 1056982 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 198232 RingCT/type: yes/0
Extra: 01d01ecbe0ac331cb45a40db7402f85974dc9c98e8f7e37116588de662dd15134d0211000000097a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b021252e2f7df073fb67248d4c3716c2a94a2115de97bcad40ccc9a8fa494676 0.600000000000 1527411 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": 1056992, "vin": [ { "gen": { "height": 1056982 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b021252e2f7df073fb67248d4c3716c2a94a2115de97bcad40ccc9a8fa494676" } } ], "extra": [ 1, 208, 30, 203, 224, 172, 51, 28, 180, 90, 64, 219, 116, 2, 248, 89, 116, 220, 156, 152, 232, 247, 227, 113, 22, 88, 141, 230, 98, 221, 21, 19, 77, 2, 17, 0, 0, 0, 9, 122, 156, 244, 199, 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