Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b81399b9a1c37e72b2c125ccaa3ca11c3cd15354c0b76cf34510446e4753d7cf

Tx prefix hash: 9a4cf24ec4f1cb197a708d4bfd2010dd4513d4fc6b08319d21a019cd1fa561b4
Tx public key: 5a7e1793da1f8864255213559a0eb25ab20122a0be11ac8b52884e77d5e5ab9d
Timestamp: 1713938682 Timestamp [UCT]: 2024-04-24 06:04:42 Age [y:d:h:m:s]: 01:223:13:01:38
Block: 1007309 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 418451 RingCT/type: yes/0
Extra: 015a7e1793da1f8864255213559a0eb25ab20122a0be11ac8b52884e77d5e5ab9d02110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4d10a1e78c1cd7ae1615fb5b791e7abd0e05d499c0c04a8c72751aaa642af24f 0.600000000000 1468607 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": 1007319, "vin": [ { "gen": { "height": 1007309 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4d10a1e78c1cd7ae1615fb5b791e7abd0e05d499c0c04a8c72751aaa642af24f" } } ], "extra": [ 1, 90, 126, 23, 147, 218, 31, 136, 100, 37, 82, 19, 85, 154, 14, 178, 90, 178, 1, 34, 160, 190, 17, 172, 139, 82, 136, 78, 119, 213, 229, 171, 157, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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