Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8d56191001a4a6abb425dbf0ae3fe48d629f631b900bffd7c4ea4e2abd895a85

Tx prefix hash: fcf572f9ca8a6bd132e3f4d10e1672c1c161e861874c16cb257047cc40ce98ce
Tx public key: e603d93dabfd058457260f5b15a0c279000922d3e5a02de873af88efed6da711
Timestamp: 1732094036 Timestamp [UCT]: 2024-11-20 09:13:56 Age [y:d:h:m:s]: 00:125:18:54:17
Block: 1157717 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 89708 RingCT/type: yes/0
Extra: 01e603d93dabfd058457260f5b15a0c279000922d3e5a02de873af88efed6da7110211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 132ea9a86d298732425159de4ac5e5054affbc35b349802a5fdf15ab13f1e5c0 0.600000000000 1643340 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": 1157727, "vin": [ { "gen": { "height": 1157717 } } ], "vout": [ { "amount": 600000000, "target": { "key": "132ea9a86d298732425159de4ac5e5054affbc35b349802a5fdf15ab13f1e5c0" } } ], "extra": [ 1, 230, 3, 217, 61, 171, 253, 5, 132, 87, 38, 15, 91, 21, 160, 194, 121, 0, 9, 34, 211, 229, 160, 45, 232, 115, 175, 136, 239, 237, 109, 167, 17, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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