Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2b09919396ebc9149cd5cc632711041747f44731d926f9d0c71c62b933ea05e7

Tx prefix hash: 864b7322645fc90299f520f390ccf3d80130e8ba5cc53b3b686b7f99b8cbf337
Tx public key: 847fd29b77767fbe8c11bcfc6a499dcea9b6697be21f0198807e068d2396a847
Timestamp: 1706990304 Timestamp [UCT]: 2024-02-03 19:58:24 Age [y:d:h:m:s]: 01:065:15:45:11
Block: 949682 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 308001 RingCT/type: yes/0
Extra: 01847fd29b77767fbe8c11bcfc6a499dcea9b6697be21f0198807e068d2396a8470211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 49d5b3252b5f4bf08f502c93afcaf2aa1a10bb877937e141fd767a616a8b4ef2 0.600000000000 1408212 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": 949692, "vin": [ { "gen": { "height": 949682 } } ], "vout": [ { "amount": 600000000, "target": { "key": "49d5b3252b5f4bf08f502c93afcaf2aa1a10bb877937e141fd767a616a8b4ef2" } } ], "extra": [ 1, 132, 127, 210, 155, 119, 118, 127, 190, 140, 17, 188, 252, 106, 73, 157, 206, 169, 182, 105, 123, 226, 31, 1, 152, 128, 126, 6, 141, 35, 150, 168, 71, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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