Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d34e7b763fb965649b25ca2dd783fc4eb16c672b8b88f435e16b628883f21dad

Tx prefix hash: 6aa504ecb8b8310dcaa29966dc6e6005ee52bc184435966e82a9c42aa3a586b3
Tx public key: be7461f2c7cda92f8bdcda0380ff13ddd42957632ff3217f8a3c3dcfbd92e9c3
Timestamp: 1722458100 Timestamp [UCT]: 2024-07-31 20:35:00 Age [y:d:h:m:s]: 00:320:11:14:33
Block: 1077927 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 228880 RingCT/type: yes/0
Extra: 01be7461f2c7cda92f8bdcda0380ff13ddd42957632ff3217f8a3c3dcfbd92e9c302110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b38ba57db03d784f95d4547a772f0f9bfc047aa3d717449974dcdb355b8d6cbe 0.600000000000 1550482 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": 1077937, "vin": [ { "gen": { "height": 1077927 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b38ba57db03d784f95d4547a772f0f9bfc047aa3d717449974dcdb355b8d6cbe" } } ], "extra": [ 1, 190, 116, 97, 242, 199, 205, 169, 47, 139, 220, 218, 3, 128, 255, 19, 221, 212, 41, 87, 99, 47, 243, 33, 127, 138, 60, 61, 207, 189, 146, 233, 195, 2, 17, 0, 0, 0, 4, 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