Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f5be0b9309026e7e9ed24954ae6777e56323d2a5fcd798753b64aa8f2e59251f

Tx prefix hash: 4b4f643ab5926ccc3cc5445a2774af4337cd31df59094f79c19c142d5ffc1420
Tx public key: 89b3c9d07056acf310f7fa002ab7fe1a47e8c9ae21237b32591305e9ee9cab6c
Timestamp: 1582551429 Timestamp [UCT]: 2020-02-24 13:37:09 Age [y:d:h:m:s]: 04:276:16:59:31
Block: 71648 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1090295 RingCT/type: yes/0
Extra: 0189b3c9d07056acf310f7fa002ab7fe1a47e8c9ae21237b32591305e9ee9cab6c0211000000284943cd9f000000000000000000

1 output(s) for total of 355.304931000000 dcy

stealth address amount amount idx
00: 75adc9ac72404d5d47a701c5d94dbea607ecb6db5a2ae8d1660b897ab7685054 355.304931000000 132359 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": 71658, "vin": [ { "gen": { "height": 71648 } } ], "vout": [ { "amount": 355304931000, "target": { "key": "75adc9ac72404d5d47a701c5d94dbea607ecb6db5a2ae8d1660b897ab7685054" } } ], "extra": [ 1, 137, 179, 201, 208, 112, 86, 172, 243, 16, 247, 250, 0, 42, 183, 254, 26, 71, 232, 201, 174, 33, 35, 123, 50, 89, 19, 5, 233, 238, 156, 171, 108, 2, 17, 0, 0, 0, 40, 73, 67, 205, 159, 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