Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 71b6da4e5c5baedb888c89c97c08318eef83a0feeff90dd5462bdafb6a2e964e

Tx prefix hash: 9b657626420f80ae46136127cbffc20da678557754b39a7cc44b413411cc4090
Tx public key: 5b8e04ce7af1c3f9a19c85bec1c453913b70df3afde5bfde7f051398d4d62dd0
Timestamp: 1720947415 Timestamp [UCT]: 2024-07-14 08:56:55 Age [y:d:h:m:s]: 01:120:17:11:39
Block: 1065422 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 344779 RingCT/type: yes/0
Extra: 015b8e04ce7af1c3f9a19c85bec1c453913b70df3afde5bfde7f051398d4d62dd002110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 45745ebcb1b9a66979031cc0563eb6ca1d12e896e79f14920e9d6d9e53dd744d 0.600000000000 1535967 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": 1065432, "vin": [ { "gen": { "height": 1065422 } } ], "vout": [ { "amount": 600000000, "target": { "key": "45745ebcb1b9a66979031cc0563eb6ca1d12e896e79f14920e9d6d9e53dd744d" } } ], "extra": [ 1, 91, 142, 4, 206, 122, 241, 195, 249, 161, 156, 133, 190, 193, 196, 83, 145, 59, 112, 223, 58, 253, 229, 191, 222, 127, 5, 19, 152, 212, 214, 45, 208, 2, 17, 0, 0, 0, 7, 145, 225, 60, 4, 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