Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8d7e97d223365f8c595cf3db4f331f8ca98a6b5b09fcc6b08079d41120d284ea

Tx prefix hash: 6feff00a1ce2fa0753cd0586690e50dfe3b49cf0875ae9596bb437848eb0daa4
Tx public key: 669c486c9152d772b461f27fcec75f4c9852e49fa2d38228aea9b654be9fa071
Timestamp: 1738485300 Timestamp [UCT]: 2025-02-02 08:35:00 Age [y:d:h:m:s]: 00:338:10:49:59
Block: 1210377 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 239723 RingCT/type: yes/0
Extra: 01669c486c9152d772b461f27fcec75f4c9852e49fa2d38228aea9b654be9fa071021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3b6b13a96d807a9bec704dae4677d37c7a371f8819cff0a8d2bb5e970c7f5305 0.600000000000 1697128 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": 1210387, "vin": [ { "gen": { "height": 1210377 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3b6b13a96d807a9bec704dae4677d37c7a371f8819cff0a8d2bb5e970c7f5305" } } ], "extra": [ 1, 102, 156, 72, 108, 145, 82, 215, 114, 180, 97, 242, 127, 206, 199, 95, 76, 152, 82, 228, 159, 162, 211, 130, 40, 174, 169, 182, 84, 190, 159, 160, 113, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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