Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 64dd1ab8e4d3663883138752dd2d5ab44882ea798c8bbff36359452c2c98680a

Tx prefix hash: 2ce2770183960b0cb91a2a93ea162375e1388fa83b4cbde7ee959d38b49a6b02
Tx public key: b846ae989d4e6923eb97e93c3a2633b97b883771ccec7dfc9aab1c84a1b07a2e
Timestamp: 1725457953 Timestamp [UCT]: 2024-09-04 13:52:33 Age [y:d:h:m:s]: 00:218:08:57:20
Block: 1102815 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 155903 RingCT/type: yes/0
Extra: 01b846ae989d4e6923eb97e93c3a2633b97b883771ccec7dfc9aab1c84a1b07a2e02110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2053f9042064e3dbc5077e89bc7f7ea584c1af118d8d7917fa32cedd2eea646e 0.600000000000 1579394 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": 1102825, "vin": [ { "gen": { "height": 1102815 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2053f9042064e3dbc5077e89bc7f7ea584c1af118d8d7917fa32cedd2eea646e" } } ], "extra": [ 1, 184, 70, 174, 152, 157, 78, 105, 35, 235, 151, 233, 60, 58, 38, 51, 185, 123, 136, 55, 113, 204, 236, 125, 252, 154, 171, 28, 132, 161, 176, 122, 46, 2, 17, 0, 0, 0, 6, 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