Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9cc1730a7a5d6358e0d7db9d9ee5cb96b3f653d9d24e9073ccd403edcdc95d49

Tx prefix hash: 8df4441fef70c7714ecbe5f5b3c2bc2cc77b3b8b3b121b4ffc2f48c91648e619
Tx public key: 0e9e86f8173963f74c7f4746f43e77f73fba89bd1c9e9b8dc49d0c3e48c09fc1
Timestamp: 1721164341 Timestamp [UCT]: 2024-07-16 21:12:21 Age [y:d:h:m:s]: 01:113:17:03:31
Block: 1067220 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 339761 RingCT/type: yes/0
Extra: 010e9e86f8173963f74c7f4746f43e77f73fba89bd1c9e9b8dc49d0c3e48c09fc102110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 87c50b8dc208f8793e96ce41cacbe791de55b0445910da3e67073080239aabbb 0.600000000000 1537975 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": 1067230, "vin": [ { "gen": { "height": 1067220 } } ], "vout": [ { "amount": 600000000, "target": { "key": "87c50b8dc208f8793e96ce41cacbe791de55b0445910da3e67073080239aabbb" } } ], "extra": [ 1, 14, 158, 134, 248, 23, 57, 99, 247, 76, 127, 71, 70, 244, 62, 119, 247, 63, 186, 137, 189, 28, 158, 155, 141, 196, 157, 12, 62, 72, 192, 159, 193, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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