Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 136f768d97a0e5085703c93b06d435a69e1344fa77273da0dbf852a7fdaa7078

Tx prefix hash: b77aa238b40763a1aaaca73f19bdeec0d8d3e63178008d68f5e2d3176278d1bd
Tx public key: e47a10135eb029b510cbd17b1977916aa2730953a14581706d07bc4a479e9692
Timestamp: 1582053157 Timestamp [UCT]: 2020-02-18 19:12:37 Age [y:d:h:m:s]: 05:256:11:26:27
Block: 67701 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1334053 RingCT/type: yes/0
Extra: 01e47a10135eb029b510cbd17b1977916aa2730953a14581706d07bc4a479e96920211000000044943cd9f000000000000000000

1 output(s) for total of 366.181454311000 dcy

stealth address amount amount idx
00: 5ebbd9668bd1cd7a1c7faa3fe723a64d4dc020b6c8e7943a2bfceab34e255c1b 366.181454311000 124688 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": 67711, "vin": [ { "gen": { "height": 67701 } } ], "vout": [ { "amount": 366181454311, "target": { "key": "5ebbd9668bd1cd7a1c7faa3fe723a64d4dc020b6c8e7943a2bfceab34e255c1b" } } ], "extra": [ 1, 228, 122, 16, 19, 94, 176, 41, 181, 16, 203, 209, 123, 25, 119, 145, 106, 162, 115, 9, 83, 161, 69, 129, 112, 109, 7, 188, 74, 71, 158, 150, 146, 2, 17, 0, 0, 0, 4, 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