Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3807ec22d8fb42669c6fb0cf19a411177bbc62184bd310a783dae0a97758a173

Tx prefix hash: a77a8ec2d3def2dcecb1a60e336e5081e052c05b267d4377ce3048c8628bb6b8
Tx public key: 1f7427f6f28af22b6bdb95df29f7b901136944417aff21b01f9ef02cb88a4476
Timestamp: 1725118294 Timestamp [UCT]: 2024-08-31 15:31:34 Age [y:d:h:m:s]: 00:085:07:52:45
Block: 1099982 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 61030 RingCT/type: yes/0
Extra: 011f7427f6f28af22b6bdb95df29f7b901136944417aff21b01f9ef02cb88a447602110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 35428abf9f6371b32f9250bf0ccd47dc61398e4d1ec23f5ad2f4583781b5d1c6 0.600000000000 1575953 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": 1099992, "vin": [ { "gen": { "height": 1099982 } } ], "vout": [ { "amount": 600000000, "target": { "key": "35428abf9f6371b32f9250bf0ccd47dc61398e4d1ec23f5ad2f4583781b5d1c6" } } ], "extra": [ 1, 31, 116, 39, 246, 242, 138, 242, 43, 107, 219, 149, 223, 41, 247, 185, 1, 19, 105, 68, 65, 122, 255, 33, 176, 31, 158, 240, 44, 184, 138, 68, 118, 2, 17, 0, 0, 0, 1, 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