Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a62862872cdd6087c82ac24d1747e110d3a9e9e08631d5c00859a8147bd39217

Tx prefix hash: 660b24c2730910823e5986cf08492636614faad2ffbb9abaea2224eb59c69625
Tx public key: a42505d74146f7d946cd81ed1f3b04c96c8db73fb9cd9e3bfc8f91ac4468b1e5
Timestamp: 1736018351 Timestamp [UCT]: 2025-01-04 19:19:11 Age [y:d:h:m:s]: 00:164:03:36:13
Block: 1190227 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 117019 RingCT/type: yes/0
Extra: 01a42505d74146f7d946cd81ed1f3b04c96c8db73fb9cd9e3bfc8f91ac4468b1e502110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 896724076d295cb3d9ac09cb3574e7bdedcc05e88dd9e663b24584822ccb9dbb 0.600000000000 1676742 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": 1190237, "vin": [ { "gen": { "height": 1190227 } } ], "vout": [ { "amount": 600000000, "target": { "key": "896724076d295cb3d9ac09cb3574e7bdedcc05e88dd9e663b24584822ccb9dbb" } } ], "extra": [ 1, 164, 37, 5, 215, 65, 70, 247, 217, 70, 205, 129, 237, 31, 59, 4, 201, 108, 141, 183, 63, 185, 205, 158, 59, 252, 143, 145, 172, 68, 104, 177, 229, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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