Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9f79bcebe6fa917e423081de34ea13413c90c7d0d533a9a89cad245f8ce8e863

Tx prefix hash: 766794c58a1bdba1f733517939c550a40311320feaa54cb5a3bbcfddac7d4526
Tx public key: 9029620e24ee00204eb1f1a769cd98ae39dc1e7e1e50879bcd43172fb6ec5a32
Timestamp: 1716013678 Timestamp [UCT]: 2024-05-18 06:27:58 Age [y:d:h:m:s]: 00:327:00:14:20
Block: 1024508 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 233738 RingCT/type: yes/0
Extra: 019029620e24ee00204eb1f1a769cd98ae39dc1e7e1e50879bcd43172fb6ec5a3202110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: be47328cadf78dfc51e6482f74f4a3bad8fb47182ed3920e045d52c6f486992f 0.600000000000 1490309 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": 1024518, "vin": [ { "gen": { "height": 1024508 } } ], "vout": [ { "amount": 600000000, "target": { "key": "be47328cadf78dfc51e6482f74f4a3bad8fb47182ed3920e045d52c6f486992f" } } ], "extra": [ 1, 144, 41, 98, 14, 36, 238, 0, 32, 78, 177, 241, 167, 105, 205, 152, 174, 57, 220, 30, 126, 30, 80, 135, 155, 205, 67, 23, 47, 182, 236, 90, 50, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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