Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 097eca82be1cac376ba697507cfef63381cdf6ec5229ebe6956b5d4c980d9cf7

Tx prefix hash: eaf8163ae9b9107035fc525714d1cefd0ec64e60ed7124b8c96d1ba092be342a
Tx public key: 3a887393021cf1d3ef0b310b7dff17b9c1b27acb5d8eb6bc4fb6c166b0f6c774
Timestamp: 1712655532 Timestamp [UCT]: 2024-04-09 09:38:52 Age [y:d:h:m:s]: 01:049:21:17:28
Block: 996641 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 296683 RingCT/type: yes/0
Extra: 013a887393021cf1d3ef0b310b7dff17b9c1b27acb5d8eb6bc4fb6c166b0f6c7740211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a44b28ad1fc025f41664a698536be930910a39d5f974f36912af6bb352d726aa 0.600000000000 1457067 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": 996651, "vin": [ { "gen": { "height": 996641 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a44b28ad1fc025f41664a698536be930910a39d5f974f36912af6bb352d726aa" } } ], "extra": [ 1, 58, 136, 115, 147, 2, 28, 241, 211, 239, 11, 49, 11, 125, 255, 23, 185, 193, 178, 122, 203, 93, 142, 182, 188, 79, 182, 193, 102, 176, 246, 199, 116, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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