Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bdfb9b28f6a63e5aa98f6c96cc67643b0eaebe0ac910406366e3d8f401c1d6b3

Tx prefix hash: 411ee251b6a2c72fc5b0c41887fc8f71078fe04b5808d6b8184ad35ce8183014
Tx public key: d7c10171ecd21b996e1044cc9a7f7256b6339cc045633feae7ab29ff37584008
Timestamp: 1731704375 Timestamp [UCT]: 2024-11-15 20:59:35 Age [y:d:h:m:s]: 00:008:09:45:22
Block: 1154495 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 6016 RingCT/type: yes/0
Extra: 01d7c10171ecd21b996e1044cc9a7f7256b6339cc045633feae7ab29ff375840080211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 284e557c0ed1b618e616fad7e30ad2bd39e8f60541fc96a9cc9e5b17f05aa099 0.600000000000 1640108 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": 1154505, "vin": [ { "gen": { "height": 1154495 } } ], "vout": [ { "amount": 600000000, "target": { "key": "284e557c0ed1b618e616fad7e30ad2bd39e8f60541fc96a9cc9e5b17f05aa099" } } ], "extra": [ 1, 215, 193, 1, 113, 236, 210, 27, 153, 110, 16, 68, 204, 154, 127, 114, 86, 182, 51, 156, 192, 69, 99, 63, 234, 231, 171, 41, 255, 55, 88, 64, 8, 2, 17, 0, 0, 0, 7, 31, 10, 83, 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