Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 64c4d66d6cdc9590619f9f0314a6c50fc1c8b23a9774c54ab94b567c27b433bc

Tx prefix hash: 80e1836959bb7d062da27821cafaa11dea1c4b5f14b3ee9a93796fdf56e58f9d
Tx public key: f8267e6ce55fc4cb71a88eed921bf5f484c83257acd2a224237451d95681cf3f
Timestamp: 1722656572 Timestamp [UCT]: 2024-08-03 03:42:52 Age [y:d:h:m:s]: 00:241:02:45:21
Block: 1079586 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 172207 RingCT/type: yes/0
Extra: 01f8267e6ce55fc4cb71a88eed921bf5f484c83257acd2a224237451d95681cf3f021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 89ba706b957d803f4c134c22ea9af1bdfae0de498c95a53ed1df99490725cd4c 0.600000000000 1552599 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": 1079596, "vin": [ { "gen": { "height": 1079586 } } ], "vout": [ { "amount": 600000000, "target": { "key": "89ba706b957d803f4c134c22ea9af1bdfae0de498c95a53ed1df99490725cd4c" } } ], "extra": [ 1, 248, 38, 126, 108, 229, 95, 196, 203, 113, 168, 142, 237, 146, 27, 245, 244, 132, 200, 50, 87, 172, 210, 162, 36, 35, 116, 81, 217, 86, 129, 207, 63, 2, 17, 0, 0, 0, 7, 233, 20, 221, 21, 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