Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4d5d6dbcba48e3f4194fd611d97c1e69b04ea2bdf69db243cb1f880ab5560570

Tx prefix hash: 0db719c19152fd34c52ac9458a08af34b7b6cac6123f53c4f478b8e8b10def50
Tx public key: 637619aac4646ec1656d9cf0a30a434accec46cb07485b0a768b78ea0f24cfbf
Timestamp: 1673083556 Timestamp [UCT]: 2023-01-07 09:25:56 Age [y:d:h:m:s]: 02:143:18:07:37
Block: 669446 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 624481 RingCT/type: yes/0
Extra: 01637619aac4646ec1656d9cf0a30a434accec46cb07485b0a768b78ea0f24cfbf02110000000252542ceb000000000000000000

1 output(s) for total of 3.714047552000 dcy

stealth address amount amount idx
00: 58b00bcda5a8d7fc19de22841faf88352ce1b3875db2f52dc711fc3a05d668e8 3.714047552000 1110763 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 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": 669456, "vin": [ { "gen": { "height": 669446 } } ], "vout": [ { "amount": 3714047552, "target": { "key": "58b00bcda5a8d7fc19de22841faf88352ce1b3875db2f52dc711fc3a05d668e8" } } ], "extra": [ 1, 99, 118, 25, 170, 196, 100, 110, 193, 101, 109, 156, 240, 163, 10, 67, 74, 204, 236, 70, 203, 7, 72, 91, 10, 118, 139, 120, 234, 15, 36, 207, 191, 2, 17, 0, 0, 0, 2, 82, 84, 44, 235, 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