Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 66ae0f567e2bcb72ff0c0ce2c6d7acdd16abc6dab8152c5120311d1c3311951b

Tx prefix hash: 837b9a01e06f744650a664c2b3cdfb2985041d633aaef9c03aa8b35b799c0488
Tx public key: 2b7a2240b869a496d67b38340405461bcf2d09a8e4328ecc2fb2fe1f23c4b321
Timestamp: 1754999500 Timestamp [UCT]: 2025-08-12 11:51:40 Age [y:d:h:m:s]: 00:106:02:05:28
Block: 1345437 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 75139 RingCT/type: yes/0
Extra: 012b7a2240b869a496d67b38340405461bcf2d09a8e4328ecc2fb2fe1f23c4b32102110000000fb2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a223d68a7d76a9c6fd26ea1e10cfe1f9ab223f15b6ded4df76c9d545e9c3a358 0.600000000000 1833330 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": 1345447, "vin": [ { "gen": { "height": 1345437 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a223d68a7d76a9c6fd26ea1e10cfe1f9ab223f15b6ded4df76c9d545e9c3a358" } } ], "extra": [ 1, 43, 122, 34, 64, 184, 105, 164, 150, 214, 123, 56, 52, 4, 5, 70, 27, 207, 45, 9, 168, 228, 50, 142, 204, 47, 178, 254, 31, 35, 196, 179, 33, 2, 17, 0, 0, 0, 15, 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