Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 980bf2fd8297638e847882c0b931128a65ccf43c95e17733e97dc52541120173

Tx prefix hash: 89ceb6f69edb7ba1c10cb809a7b0070a87a9b25117c1926dfb8014c3d5aa59fc
Tx public key: c2cfca9c7ffb5026b5d119179eb2814f8da5f89d7379ecc60b13d6bac612c13e
Timestamp: 1709498656 Timestamp [UCT]: 2024-03-03 20:44:16 Age [y:d:h:m:s]: 01:060:09:34:06
Block: 970505 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 304181 RingCT/type: yes/0
Extra: 01c2cfca9c7ffb5026b5d119179eb2814f8da5f89d7379ecc60b13d6bac612c13e0211000000080011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c5c5cc41588c22a91fbe20f90e26e7e95ce21ada240d7697f5eed9a5e7064d3e 0.600000000000 1430362 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": 970515, "vin": [ { "gen": { "height": 970505 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c5c5cc41588c22a91fbe20f90e26e7e95ce21ada240d7697f5eed9a5e7064d3e" } } ], "extra": [ 1, 194, 207, 202, 156, 127, 251, 80, 38, 181, 209, 25, 23, 158, 178, 129, 79, 141, 165, 248, 157, 115, 121, 236, 198, 11, 19, 214, 186, 198, 18, 193, 62, 2, 17, 0, 0, 0, 8, 0, 17, 5, 91, 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