Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2ebb0a620a5c1fda03ed617bb5e0e28f70bb96774c3f318cb1f27a3d3029c9e9

Tx prefix hash: 18cc01fe2011ae9588e7a3abd64c1cbacea699c3405e6072fc233da3c7eebf9f
Tx public key: e7be5745c54a07492310deadefc506a6c738c5ef1e8dd2b3ad15c9471d321d71
Timestamp: 1720460751 Timestamp [UCT]: 2024-07-08 17:45:51 Age [y:d:h:m:s]: 00:279:04:40:22
Block: 1061383 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 199490 RingCT/type: yes/0
Extra: 01e7be5745c54a07492310deadefc506a6c738c5ef1e8dd2b3ad15c9471d321d7102110000000ae914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c7ddc47d643deabd34ab2d259fddf71e7a27456a6df7524d9438dae8514fb0af 0.600000000000 1531874 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": 1061393, "vin": [ { "gen": { "height": 1061383 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c7ddc47d643deabd34ab2d259fddf71e7a27456a6df7524d9438dae8514fb0af" } } ], "extra": [ 1, 231, 190, 87, 69, 197, 74, 7, 73, 35, 16, 222, 173, 239, 197, 6, 166, 199, 56, 197, 239, 30, 141, 210, 179, 173, 21, 201, 71, 29, 50, 29, 113, 2, 17, 0, 0, 0, 10, 233, 20, 221, 21, 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