Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dfa4921507e917d6020f27ba24a7ef829d79df36792b5dd72b6abe808d722f34

Tx prefix hash: cf0112ba408c1f894eebe74cdbb6421bcfcc23c652fa355942da9707a05c1ee7
Tx public key: bb9dafaab1d0cfda59eb0800195fb74d9ec2ef0e28f1fc47d786cf4b049faad4
Timestamp: 1677235160 Timestamp [UCT]: 2023-02-24 10:39:20 Age [y:d:h:m:s]: 02:112:01:26:25
Block: 703894 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 601623 RingCT/type: yes/0
Extra: 01bb9dafaab1d0cfda59eb0800195fb74d9ec2ef0e28f1fc47d786cf4b049faad402110000000774b6d784000000000000000000

1 output(s) for total of 2.856592545000 dcy

stealth address amount amount idx
00: 4ef7de1caa7cac9a85f92cb5082d93376335b98d0da53b7d5c6be5c9f2cd9ad8 2.856592545000 1147521 of 0

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": 703904, "vin": [ { "gen": { "height": 703894 } } ], "vout": [ { "amount": 2856592545, "target": { "key": "4ef7de1caa7cac9a85f92cb5082d93376335b98d0da53b7d5c6be5c9f2cd9ad8" } } ], "extra": [ 1, 187, 157, 175, 170, 177, 208, 207, 218, 89, 235, 8, 0, 25, 95, 183, 77, 158, 194, 239, 14, 40, 241, 252, 71, 215, 134, 207, 75, 4, 159, 170, 212, 2, 17, 0, 0, 0, 7, 116, 182, 215, 132, 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