Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cb0b7b4ade672d548df4f318924bc02bdc8b37a0f9325df4e10b986d710255c2

Tx prefix hash: 622a92232e5e54b37d0c57196ad19245c37e6f5f5e58da3d3ad5ee58026114cf
Tx public key: 4eac8ee83af3037f54c2b6b84649bf6cd7b54fc612928df2c11e84ff84750179
Timestamp: 1735965142 Timestamp [UCT]: 2025-01-04 04:32:22 Age [y:d:h:m:s]: 00:093:12:59:31
Block: 1189787 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 66623 RingCT/type: yes/0
Extra: 014eac8ee83af3037f54c2b6b84649bf6cd7b54fc612928df2c11e84ff847501790211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: da9b844a812d851c7e0310be9cd11639a1cca34d1d26618cf62d6ed367d0b2c3 0.600000000000 1676298 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": 1189797, "vin": [ { "gen": { "height": 1189787 } } ], "vout": [ { "amount": 600000000, "target": { "key": "da9b844a812d851c7e0310be9cd11639a1cca34d1d26618cf62d6ed367d0b2c3" } } ], "extra": [ 1, 78, 172, 142, 232, 58, 243, 3, 127, 84, 194, 182, 184, 70, 73, 191, 108, 215, 181, 79, 198, 18, 146, 141, 242, 193, 30, 132, 255, 132, 117, 1, 121, 2, 17, 0, 0, 0, 7, 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