Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ca0344d0adf7d8a7514e94a82de36e7ce81c8a481e449cdddf9c719e8b616f6f

Tx prefix hash: 8739054cfa18e75dd231bfd688a0d6796854533668aed892fe553a0e13b3fa3a
Tx public key: b3e165c1c3aa0b6ac0bb8c7123983a606971481e6d69c7da4bf16bb5dc108065
Timestamp: 1750876783 Timestamp [UCT]: 2025-06-25 18:39:43 Age [y:d:h:m:s]: 00:214:23:34:16
Block: 1312669 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 151542 RingCT/type: yes/0
Extra: 01b3e165c1c3aa0b6ac0bb8c7123983a606971481e6d69c7da4bf16bb5dc108065021100000010bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bcf5b3710f7a403e22253486f54f061c25173eed60a2032d3f99a617e165f459 0.600000000000 1800304 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": 1312679, "vin": [ { "gen": { "height": 1312669 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bcf5b3710f7a403e22253486f54f061c25173eed60a2032d3f99a617e165f459" } } ], "extra": [ 1, 179, 225, 101, 193, 195, 170, 11, 106, 192, 187, 140, 113, 35, 152, 58, 96, 105, 113, 72, 30, 109, 105, 199, 218, 75, 241, 107, 181, 220, 16, 128, 101, 2, 17, 0, 0, 0, 16, 191, 81, 178, 162, 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