Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e2313ec8a8b0160fbaf6ef1b798b2c46a3c835af944bce8d614f6b126d088d1d

Tx prefix hash: d4e86e60f32d03852380274a0b8954d28e560596512ee3a5308185ca20be30ab
Tx public key: 7ef79fdf19d7ba4466c745ce2c36a9fb7715eb1a9f1e70d9191d2ebda9e446ce
Timestamp: 1762472229 Timestamp [UCT]: 2025-11-06 23:37:09 Age [y:d:h:m:s]: 00:046:17:59:11
Block: 1406537 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 33473 RingCT/type: yes/0
Extra: 017ef79fdf19d7ba4466c745ce2c36a9fb7715eb1a9f1e70d9191d2ebda9e446ce0211000000038368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 390c0f02082c66f719f83a0faf35ed667d6896f87fab316391051b3282da0a48 0.600000000000 1894924 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": 1406547, "vin": [ { "gen": { "height": 1406537 } } ], "vout": [ { "amount": 600000000, "target": { "key": "390c0f02082c66f719f83a0faf35ed667d6896f87fab316391051b3282da0a48" } } ], "extra": [ 1, 126, 247, 159, 223, 25, 215, 186, 68, 102, 199, 69, 206, 44, 54, 169, 251, 119, 21, 235, 26, 159, 30, 112, 217, 25, 29, 46, 189, 169, 228, 70, 206, 2, 17, 0, 0, 0, 3, 131, 104, 38, 109, 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