Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a2e4985fe97c11b13a70144ba8f3f71b67249f009a99de3a771adec523bc138b

Tx prefix hash: 965e9e2b9e1bfea4297445cd73a9738b13d4f409651b4b4d6889be255dce2c36
Tx public key: 6719f30e13e3002e949ba3d3f16f96ccf3c64062c0074c82b6d0e7418d4c5243
Timestamp: 1578968579 Timestamp [UCT]: 2020-01-14 02:22:59 Age [y:d:h:m:s]: 05:045:17:07:17
Block: 45091 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1182767 RingCT/type: yes/0
Extra: 016719f30e13e3002e949ba3d3f16f96ccf3c64062c0074c82b6d0e7418d4c524302110000000e4943cd9f000000000000000000

1 output(s) for total of 435.106567926000 dcy

stealth address amount amount idx
00: 0c918a61b1a4609d893ba667e2a6aedfa4e5c73a7fe485367a5f52a3f12c6b4c 435.106567926000 82251 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": 45101, "vin": [ { "gen": { "height": 45091 } } ], "vout": [ { "amount": 435106567926, "target": { "key": "0c918a61b1a4609d893ba667e2a6aedfa4e5c73a7fe485367a5f52a3f12c6b4c" } } ], "extra": [ 1, 103, 25, 243, 14, 19, 227, 0, 46, 148, 155, 163, 211, 241, 111, 150, 204, 243, 198, 64, 98, 192, 7, 76, 130, 182, 208, 231, 65, 141, 76, 82, 67, 2, 17, 0, 0, 0, 14, 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