Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aaf533898afd991097ae08cb50dedac2eed27a5b0023f7ec67e247eefe4a87fe

Tx prefix hash: eb8bbc830c79b9a42a435d85614b53f97fd66525c216ef91a041ef01a9e4f486
Tx public key: 6a597097c7dcb39134219e431b0d7656e23baa1bd8a452f7cb6fd86cc6573380
Timestamp: 1708331710 Timestamp [UCT]: 2024-02-19 08:35:10 Age [y:d:h:m:s]: 01:094:14:42:04
Block: 960817 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 328687 RingCT/type: yes/0
Extra: 016a597097c7dcb39134219e431b0d7656e23baa1bd8a452f7cb6fd86cc657338002110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e672f047243bf95e0e5e7c02c2161a9590a88ae448a9dbcad373e95e8d279c9e 0.600000000000 1420404 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": 960827, "vin": [ { "gen": { "height": 960817 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e672f047243bf95e0e5e7c02c2161a9590a88ae448a9dbcad373e95e8d279c9e" } } ], "extra": [ 1, 106, 89, 112, 151, 199, 220, 179, 145, 52, 33, 158, 67, 27, 13, 118, 86, 226, 59, 170, 27, 216, 164, 82, 247, 203, 111, 216, 108, 198, 87, 51, 128, 2, 17, 0, 0, 0, 4, 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