Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8f604d0190def13a254796afb954182098f51468e6c7fddd64a403365c7157e3

Tx prefix hash: da4326b44a1dea35b7516b0f9e504cf005956047533484864212509ffdbf34cb
Tx public key: b920c7186c6d06b178f6bb19e8efa1571988f2df09a4c8ca79e83c249fc0038f
Timestamp: 1682886470 Timestamp [UCT]: 2023-04-30 20:27:50 Age [y:d:h:m:s]: 01:262:09:31:43
Block: 750119 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 449002 RingCT/type: yes/0
Extra: 01b920c7186c6d06b178f6bb19e8efa1571988f2df09a4c8ca79e83c249fc0038f021100000002b3164c24000000000000000000

1 output(s) for total of 2.006987034000 dcy

stealth address amount amount idx
00: 3c0c563e531b7385d037eb18dbd5a3b513f92db82e1091e8a816eec929432000 2.006987034000 1198160 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": 750129, "vin": [ { "gen": { "height": 750119 } } ], "vout": [ { "amount": 2006987034, "target": { "key": "3c0c563e531b7385d037eb18dbd5a3b513f92db82e1091e8a816eec929432000" } } ], "extra": [ 1, 185, 32, 199, 24, 108, 109, 6, 177, 120, 246, 187, 25, 232, 239, 161, 87, 25, 136, 242, 223, 9, 164, 200, 202, 121, 232, 60, 36, 159, 192, 3, 143, 2, 17, 0, 0, 0, 2, 179, 22, 76, 36, 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