Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 652c373c1b13bf12054902bbd91c073097e16cdd72ab91110057ffe919c5e7e5

Tx prefix hash: eed23a7ecf8210c26af941ee2a2bce71d89515d0ad9229149a4d2107b688a5b6
Tx public key: 403289ff71e774fb7a72117a89e1f0a7df627839d7a2f64b042bbccb70eff766
Timestamp: 1730155662 Timestamp [UCT]: 2024-10-28 22:47:42 Age [y:d:h:m:s]: 00:151:01:31:19
Block: 1141686 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 107788 RingCT/type: yes/0
Extra: 01403289ff71e774fb7a72117a89e1f0a7df627839d7a2f64b042bbccb70eff766021100000004a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e4acdde7e3ae3504e6b67de2e433ea939f9c908d54d6525ca764e5df3d49f79d 0.600000000000 1625497 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": 1141696, "vin": [ { "gen": { "height": 1141686 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e4acdde7e3ae3504e6b67de2e433ea939f9c908d54d6525ca764e5df3d49f79d" } } ], "extra": [ 1, 64, 50, 137, 255, 113, 231, 116, 251, 122, 114, 17, 122, 137, 225, 240, 167, 223, 98, 120, 57, 215, 162, 246, 75, 4, 43, 188, 203, 112, 239, 247, 102, 2, 17, 0, 0, 0, 4, 161, 29, 186, 152, 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