Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6daacc6016b353473fc6db9a8d80463a3ce09a893061e60b4b77c365c4fa1e2a

Tx prefix hash: b18ae4c151bb0aadd7803abd43c08a37d53c8b85b8a28cab97c8cfc6e0a03c64
Tx public key: 863755630e04a02620cbf0df26081483622f6b6ee079d274bc4423a77df708b5
Timestamp: 1739389185 Timestamp [UCT]: 2025-02-12 19:39:45 Age [y:d:h:m:s]: 00:028:05:14:17
Block: 1217870 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 20185 RingCT/type: yes/0
Extra: 01863755630e04a02620cbf0df26081483622f6b6ee079d274bc4423a77df708b5021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8cfe0aafe35e67a2c40b649f6420f2c06be27ab6d96e3ab76edd22baf93e91dc 0.600000000000 1704685 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": 1217880, "vin": [ { "gen": { "height": 1217870 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8cfe0aafe35e67a2c40b649f6420f2c06be27ab6d96e3ab76edd22baf93e91dc" } } ], "extra": [ 1, 134, 55, 85, 99, 14, 4, 160, 38, 32, 203, 240, 223, 38, 8, 20, 131, 98, 47, 107, 110, 224, 121, 210, 116, 188, 68, 35, 167, 125, 247, 8, 181, 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