Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8c3ff61cc3a7abe72bd2552258d907f270e6aca7979aba28742506297122d5f6

Tx prefix hash: a91a8b36f9dd2a575d1619547b2c5ea592ca7a38eaf72c48070aef002233c34a
Tx public key: 263a116b3c0e27f9a914f9157ee1f65bd58ef5e55b7da4ba349ffc72803f628a
Timestamp: 1675489872 Timestamp [UCT]: 2023-02-04 05:51:12 Age [y:d:h:m:s]: 02:074:15:27:22
Block: 689425 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 574987 RingCT/type: yes/0
Extra: 01263a116b3c0e27f9a914f9157ee1f65bd58ef5e55b7da4ba349ffc72803f628a02110000000474b6d784000000000000000000

1 output(s) for total of 3.188957342000 dcy

stealth address amount amount idx
00: a59633ea6e618a2e117c0e93c098022d5435007d792fc47d82b0a30c1c20d662 3.188957342000 1132097 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": 689435, "vin": [ { "gen": { "height": 689425 } } ], "vout": [ { "amount": 3188957342, "target": { "key": "a59633ea6e618a2e117c0e93c098022d5435007d792fc47d82b0a30c1c20d662" } } ], "extra": [ 1, 38, 58, 17, 107, 60, 14, 39, 249, 169, 20, 249, 21, 126, 225, 246, 91, 213, 142, 245, 229, 91, 125, 164, 186, 52, 159, 252, 114, 128, 63, 98, 138, 2, 17, 0, 0, 0, 4, 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