Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a7be9a91571afcdc00ac87085f168b589e6aadfc6f2b8c90212e092393d347e1

Tx prefix hash: 69d930b148347b9e2ae507dec16bd4a0e71ebaa4c64a023f1f82abbb3765b938
Tx public key: d05e52e090e523fa5808ff4c9075ec925fd45730b78f240f0a1d0fb15480ab0f
Timestamp: 1748370936 Timestamp [UCT]: 2025-05-27 18:35:36 Age [y:d:h:m:s]: 00:176:13:25:53
Block: 1292224 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 123882 RingCT/type: yes/0
Extra: 01d05e52e090e523fa5808ff4c9075ec925fd45730b78f240f0a1d0fb15480ab0f02110000000186ae2f0d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b9c6e9fcfe6ba179fe11b4678e70293443e2dd7070eb162d53ee7cda472b30da 0.600000000000 1779695 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": 1292234, "vin": [ { "gen": { "height": 1292224 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b9c6e9fcfe6ba179fe11b4678e70293443e2dd7070eb162d53ee7cda472b30da" } } ], "extra": [ 1, 208, 94, 82, 224, 144, 229, 35, 250, 88, 8, 255, 76, 144, 117, 236, 146, 95, 212, 87, 48, 183, 143, 36, 15, 10, 29, 15, 177, 84, 128, 171, 15, 2, 17, 0, 0, 0, 1, 134, 174, 47, 13, 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