Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d771736156833d0ef446adf60ab6c918a9b20a668a1be6c80f05d06400de5197

Tx prefix hash: 652091cb968b712933e5c83f28269034529e03f9928ffe5e0f770afef0828dbc
Tx public key: b1724d3efe6d54666d462313982840ba34b89dc0e8b1482cbca7ca2d470853b6
Timestamp: 1755110081 Timestamp [UCT]: 2025-08-13 18:34:41 Age [y:d:h:m:s]: 00:049:00:38:29
Block: 1346213 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 34414 RingCT/type: yes/0
Extra: 01b1724d3efe6d54666d462313982840ba34b89dc0e8b1482cbca7ca2d470853b6021100000005b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cf9becf5c905e8eac89ea5e2dc6658ef2dc4a413c43e0534b57789744aa3c031 0.600000000000 1834112 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": 1346223, "vin": [ { "gen": { "height": 1346213 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cf9becf5c905e8eac89ea5e2dc6658ef2dc4a413c43e0534b57789744aa3c031" } } ], "extra": [ 1, 177, 114, 77, 62, 254, 109, 84, 102, 109, 70, 35, 19, 152, 40, 64, 186, 52, 184, 157, 192, 232, 177, 72, 44, 188, 167, 202, 45, 71, 8, 83, 182, 2, 17, 0, 0, 0, 5, 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