Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 29c3e5e1341a39cdda7dd1eaf2aca020427fa2cbcfebd3d8c88159c1f4224099

Tx prefix hash: f9aa73c2ca7398bfe36124749dc42c183c42e51c447d92d24d0908e6efb29286
Tx public key: a1105c32f5298a4635a2b96a6641fcdaf2aa0760833acc9b6fcf929eb678cc80
Timestamp: 1757138328 Timestamp [UCT]: 2025-09-06 05:58:48 Age [y:d:h:m:s]: 00:119:14:38:21
Block: 1362426 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 85575 RingCT/type: yes/0
Extra: 01a1105c32f5298a4635a2b96a6641fcdaf2aa0760833acc9b6fcf929eb678cc80021100000007ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 135575c46c6f2e7e75b500fb2eef59480bd9b55d2cf7ccad57389827a9d7ad7f 0.600000000000 1850457 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": 1362436, "vin": [ { "gen": { "height": 1362426 } } ], "vout": [ { "amount": 600000000, "target": { "key": "135575c46c6f2e7e75b500fb2eef59480bd9b55d2cf7ccad57389827a9d7ad7f" } } ], "extra": [ 1, 161, 16, 92, 50, 245, 41, 138, 70, 53, 162, 185, 106, 102, 65, 252, 218, 242, 170, 7, 96, 131, 58, 204, 155, 111, 207, 146, 158, 182, 120, 204, 128, 2, 17, 0, 0, 0, 7, 173, 121, 72, 208, 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