Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b19beaba9aafaff04b978fb838699bfc7a075dced23bd73f2955a51c91cbd8f4

Tx prefix hash: 36f0db62ac048ce7a1864f22e86b6b7ebad61365c7e265793bd79ca4fd270a70
Tx public key: b9fe9b4e6fb188f250db31b07c2e56d34fabb02d1304f878b421cbfc7ce58fcb
Timestamp: 1754819325 Timestamp [UCT]: 2025-08-10 09:48:45 Age [y:d:h:m:s]: 00:102:10:44:18
Block: 1344073 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 72398 RingCT/type: yes/0
Extra: 01b9fe9b4e6fb188f250db31b07c2e56d34fabb02d1304f878b421cbfc7ce58fcb021100000002b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 00c901cbae05d181ff4a0d32f77536b9de3261080611dcdf93d23d74d92bd7c2 0.600000000000 1831942 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": 1344083, "vin": [ { "gen": { "height": 1344073 } } ], "vout": [ { "amount": 600000000, "target": { "key": "00c901cbae05d181ff4a0d32f77536b9de3261080611dcdf93d23d74d92bd7c2" } } ], "extra": [ 1, 185, 254, 155, 78, 111, 177, 136, 242, 80, 219, 49, 176, 124, 46, 86, 211, 79, 171, 176, 45, 19, 4, 248, 120, 180, 33, 203, 252, 124, 229, 143, 203, 2, 17, 0, 0, 0, 2, 178, 247, 132, 196, 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