Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c0c7635ed842c687227b9e5aedacbb55d9f4784e68de83a6acf789975e7933d7

Tx prefix hash: b8eadc050acf973ae4c25d58bcebf396d9b74af5adc7cdcf6c5014a127279156
Tx public key: 10a22d24ec753e8c6f900f5385fd83438a9bee11bfbe024eb3b8b3c8c5754005
Timestamp: 1737074549 Timestamp [UCT]: 2025-01-17 00:42:29 Age [y:d:h:m:s]: 00:335:01:12:26
Block: 1198957 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 237015 RingCT/type: yes/0
Extra: 0110a22d24ec753e8c6f900f5385fd83438a9bee11bfbe024eb3b8b3c8c5754005021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8deb10876dc0039d686d8f3251228bc924c796653c46a493ad59863b1ebe6bfc 0.600000000000 1685584 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": 1198967, "vin": [ { "gen": { "height": 1198957 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8deb10876dc0039d686d8f3251228bc924c796653c46a493ad59863b1ebe6bfc" } } ], "extra": [ 1, 16, 162, 45, 36, 236, 117, 62, 140, 111, 144, 15, 83, 133, 253, 131, 67, 138, 155, 238, 17, 191, 190, 2, 78, 179, 184, 179, 200, 197, 117, 64, 5, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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