Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 99e669fff121918a245a32047f83f7dfd0c5604330da67e48932d1f3eefd902e

Tx prefix hash: e10b1b1ed595a56136e8dea2e1fe38d93f50cc4d390814803418c64a1f485aac
Tx public key: 661e3fcc423206db1d1cd6f8429dcb79da56be9f5308e74d20f60196910c07b3
Timestamp: 1755087093 Timestamp [UCT]: 2025-08-13 12:11:33 Age [y:d:h:m:s]: 00:045:06:44:59
Block: 1346055 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 31705 RingCT/type: yes/0
Extra: 01661e3fcc423206db1d1cd6f8429dcb79da56be9f5308e74d20f60196910c07b3021100000007b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b26edd2e86e4437cefc8fe2bc1b3f145e23335a644fb0b1be92b6f7b8236d914 0.600000000000 1833952 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": 1346065, "vin": [ { "gen": { "height": 1346055 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b26edd2e86e4437cefc8fe2bc1b3f145e23335a644fb0b1be92b6f7b8236d914" } } ], "extra": [ 1, 102, 30, 63, 204, 66, 50, 6, 219, 29, 28, 214, 248, 66, 157, 203, 121, 218, 86, 190, 159, 83, 8, 231, 77, 32, 246, 1, 150, 145, 12, 7, 179, 2, 17, 0, 0, 0, 7, 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