Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b73dde09bb46ba611febd06dd08b0fb971013542e1efc82cc215c8ec8732971f

Tx prefix hash: 4378baa0600cc71a59020d08579b27df3295084a814d810dd2f4cc8ec2eebc4c
Tx public key: 1ad9a26a14f5b66528214bd4e136519539f6c9f7b4dafe89d3620ae1676ae5cc
Timestamp: 1730162863 Timestamp [UCT]: 2024-10-29 00:47:43 Age [y:d:h:m:s]: 01:087:08:09:58
Block: 1141753 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 320741 RingCT/type: yes/0
Extra: 011ad9a26a14f5b66528214bd4e136519539f6c9f7b4dafe89d3620ae1676ae5cc021100000001a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 39b8a4fd5de36b5c105681f29d9e15268df572dc9fab3684850947023bd70035 0.600000000000 1625578 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": 1141763, "vin": [ { "gen": { "height": 1141753 } } ], "vout": [ { "amount": 600000000, "target": { "key": "39b8a4fd5de36b5c105681f29d9e15268df572dc9fab3684850947023bd70035" } } ], "extra": [ 1, 26, 217, 162, 106, 20, 245, 182, 101, 40, 33, 75, 212, 225, 54, 81, 149, 57, 246, 201, 247, 180, 218, 254, 137, 211, 98, 10, 225, 103, 106, 229, 204, 2, 17, 0, 0, 0, 1, 161, 29, 186, 152, 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