Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 13ed777bb3917d21938a792b2f2559c15df02c8b87b6d4594d843a1aefe8abbb

Tx prefix hash: b58d75cbb3d7347ebe649f270772a4db5198b332ffc0105cb74459b2d8128a03
Tx public key: 74b40b95171ce9483e5fa46f64407923c182a28f603e9e66ae7a16ea7c0c411e
Timestamp: 1758265381 Timestamp [UCT]: 2025-09-19 07:03:01 Age [y:d:h:m:s]: 00:069:23:51:25
Block: 1371692 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 50109 RingCT/type: yes/0
Extra: 0174b40b95171ce9483e5fa46f64407923c182a28f603e9e66ae7a16ea7c0c411e021100000003ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ef89bf976177cb851c029f59885e41c550cf806c0d986f73f99b652e01f4ed50 0.600000000000 1859769 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": 1371702, "vin": [ { "gen": { "height": 1371692 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ef89bf976177cb851c029f59885e41c550cf806c0d986f73f99b652e01f4ed50" } } ], "extra": [ 1, 116, 180, 11, 149, 23, 28, 233, 72, 62, 95, 164, 111, 100, 64, 121, 35, 193, 130, 162, 143, 96, 62, 158, 102, 174, 122, 22, 234, 124, 12, 65, 30, 2, 17, 0, 0, 0, 3, 173, 121, 72, 208, 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