Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5d00f65212cb5aab960e7ca721a7760e20d3623168f19b3ebf6c1c5f0956b317

Tx prefix hash: df3e3409d40dfc99d33049d13b45ae0ce955e3bc81185dca928da3938352f174
Tx public key: ddcad89e5e36d48e60ce597458b72929e077db0a4ed5449862a2685172a2ccb8
Timestamp: 1580212975 Timestamp [UCT]: 2020-01-28 12:02:55 Age [y:d:h:m:s]: 05:039:10:09:53
Block: 54154 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1179528 RingCT/type: yes/0
Extra: 01ddcad89e5e36d48e60ce597458b72929e077db0a4ed5449862a2685172a2ccb80211000000244ac5aa02000000000000000000

1 output(s) for total of 406.044509411000 dcy

stealth address amount amount idx
00: a705aaab507e5640be28a7124d583f9e2668f3a882e0606384a3ae0ba4ab3e6e 406.044509411000 100390 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": 54164, "vin": [ { "gen": { "height": 54154 } } ], "vout": [ { "amount": 406044509411, "target": { "key": "a705aaab507e5640be28a7124d583f9e2668f3a882e0606384a3ae0ba4ab3e6e" } } ], "extra": [ 1, 221, 202, 216, 158, 94, 54, 212, 142, 96, 206, 89, 116, 88, 183, 41, 41, 224, 119, 219, 10, 78, 213, 68, 152, 98, 162, 104, 81, 114, 162, 204, 184, 2, 17, 0, 0, 0, 36, 74, 197, 170, 2, 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