Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d6b50ac0411b97d3fddc45c6e5c9e1c9dd648eab0131aa2808ffe72febd996c7

Tx prefix hash: 856213efb0a8dd65bc0c7d8b63dce77af532c7cebd9cc08b35c91775140ef7ef
Tx public key: 1000f3625e62c3c3971867e7b4adce5fac8cb761efc28c90b5bbe3c2af06b1dc
Timestamp: 1726893801 Timestamp [UCT]: 2024-09-21 04:43:21 Age [y:d:h:m:s]: 00:000:09:46:14
Block: 1114704 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 300 RingCT/type: yes/0
Extra: 011000f3625e62c3c3971867e7b4adce5fac8cb761efc28c90b5bbe3c2af06b1dc02110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e6ec4b9634a90775307898168d80bcf8ab6ea7dbbaf0022df5ec69f60b4fe408 0.600000000000 1594577 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": 1114714, "vin": [ { "gen": { "height": 1114704 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e6ec4b9634a90775307898168d80bcf8ab6ea7dbbaf0022df5ec69f60b4fe408" } } ], "extra": [ 1, 16, 0, 243, 98, 94, 98, 195, 195, 151, 24, 103, 231, 180, 173, 206, 95, 172, 140, 183, 97, 239, 194, 140, 144, 181, 187, 227, 194, 175, 6, 177, 220, 2, 17, 0, 0, 0, 7, 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