Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9252a5c3b416d760b3581fb7bd3201f274847a8bdc4e82eb46ff1c35990abb70

Tx prefix hash: a9aeb9b6095306cba8f6264dfb39bedd0cf21d034f4744a2370a19020703c8b5
Tx public key: 0c75a694fe6d211800e98024b80f7bb2261f6ab457d413a706b8b104d6f08315
Timestamp: 1745368331 Timestamp [UCT]: 2025-04-23 00:32:11 Age [y:d:h:m:s]: 00:014:10:13:30
Block: 1267349 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 10329 RingCT/type: yes/0
Extra: 010c75a694fe6d211800e98024b80f7bb2261f6ab457d413a706b8b104d6f08315021100000001dbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b9e3b54d1aae37d235327c8874995ccdde888cf095309439f0fb0deec99131c3 0.600000000000 1754578 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": 1267359, "vin": [ { "gen": { "height": 1267349 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b9e3b54d1aae37d235327c8874995ccdde888cf095309439f0fb0deec99131c3" } } ], "extra": [ 1, 12, 117, 166, 148, 254, 109, 33, 24, 0, 233, 128, 36, 184, 15, 123, 178, 38, 31, 106, 180, 87, 212, 19, 167, 6, 184, 177, 4, 214, 240, 131, 21, 2, 17, 0, 0, 0, 1, 219, 181, 113, 193, 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