Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2e05e66a1c2c091d863b0d8979d9a551cc4714b6cc7348adc74498841db03527

Tx prefix hash: 1eb9f49bb4b539e34c22577843838733ce710889108d96c6ca8ba9ff725119c9
Tx public key: e049b71f0ecbde2cb602290b9c4375562a8a6a654daa8a6efa1b035c5d540e7a
Timestamp: 1706324714 Timestamp [UCT]: 2024-01-27 03:05:14 Age [y:d:h:m:s]: 01:029:07:49:13
Block: 944154 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 282016 RingCT/type: yes/0
Extra: 01e049b71f0ecbde2cb602290b9c4375562a8a6a654daa8a6efa1b035c5d540e7a0211000000060011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ec712d95143835adacdff2f722ec1268921e51c4d0289998b208fbfe0250d8a7 0.600000000000 1402384 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": 944164, "vin": [ { "gen": { "height": 944154 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ec712d95143835adacdff2f722ec1268921e51c4d0289998b208fbfe0250d8a7" } } ], "extra": [ 1, 224, 73, 183, 31, 14, 203, 222, 44, 182, 2, 41, 11, 156, 67, 117, 86, 42, 138, 106, 101, 77, 170, 138, 110, 250, 27, 3, 92, 93, 84, 14, 122, 2, 17, 0, 0, 0, 6, 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