Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d95e4695d89693ebdc03cb2224006f58dbaa918e7ce72da7d8ff03161d92b062

Tx prefix hash: 0601fd340d143ecab8c7915c0e3bc1b40070281681e582a7626b15a3d5d68fd2
Tx public key: ba9683a14316aa8d5e0d2ca7e195d1782f48777d165b6678f91193de5ff05cf8
Timestamp: 1580480440 Timestamp [UCT]: 2020-01-31 14:20:40 Age [y:d:h:m:s]: 05:006:15:30:36
Block: 55816 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1156620 RingCT/type: yes/0
Extra: 01ba9683a14316aa8d5e0d2ca7e195d1782f48777d165b6678f91193de5ff05cf8021100000002391a8d0e000000000000000000

1 output(s) for total of 400.921407303000 dcy

stealth address amount amount idx
00: 04250ef347da22f8b7dd81373cba475c7356470700d809405a515244d2faee7c 400.921407303000 102983 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": 55826, "vin": [ { "gen": { "height": 55816 } } ], "vout": [ { "amount": 400921407303, "target": { "key": "04250ef347da22f8b7dd81373cba475c7356470700d809405a515244d2faee7c" } } ], "extra": [ 1, 186, 150, 131, 161, 67, 22, 170, 141, 94, 13, 44, 167, 225, 149, 209, 120, 47, 72, 119, 125, 22, 91, 102, 120, 249, 17, 147, 222, 95, 240, 92, 248, 2, 17, 0, 0, 0, 2, 57, 26, 141, 14, 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