Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 62bb0ea5500e2f9b383593f29ca6c31dc8eb811d5abd0f287016906ddf12f222

Tx prefix hash: 62f0c9fc574af38110b190b4903f8015fb2e19f25e5e98e3ee8c48a80f056bf5
Tx public key: 1706e052eef752d6afc5d38083b915b99709bdb92809ea41f167e4b30194bf93
Timestamp: 1707854807 Timestamp [UCT]: 2024-02-13 20:06:47 Age [y:d:h:m:s]: 00:288:18:30:00
Block: 956861 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 206759 RingCT/type: yes/0
Extra: 011706e052eef752d6afc5d38083b915b99709bdb92809ea41f167e4b30194bf930211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e676bc75da72ae2452681e4295e2b8d83498e8f9836c6c69e91307623596d355 0.600000000000 1416173 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": 956871, "vin": [ { "gen": { "height": 956861 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e676bc75da72ae2452681e4295e2b8d83498e8f9836c6c69e91307623596d355" } } ], "extra": [ 1, 23, 6, 224, 82, 238, 247, 82, 214, 175, 197, 211, 128, 131, 185, 21, 185, 151, 9, 189, 185, 40, 9, 234, 65, 241, 103, 228, 179, 1, 148, 191, 147, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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