Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f3cc22b9d9708a7fd351f60594823731f3f1d55e482a9c563ab07ec191668b83

Tx prefix hash: 5a0a83b7ca534de6e17cea6f41831080c09d71f44adee46b229a92c15d8c522e
Tx public key: ae2adafaa126389a589c0f0eb61380d8bc019d471a826df27f838b9debbf2756
Timestamp: 1577791022 Timestamp [UCT]: 2019-12-31 11:17:02 Age [y:d:h:m:s]: 05:108:20:27:41
Block: 35663 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1227613 RingCT/type: yes/0
Extra: 01ae2adafaa126389a589c0f0eb61380d8bc019d471a826df27f838b9debbf27560211000000014943cd9f000000000000000000

1 output(s) for total of 467.556964665000 dcy

stealth address amount amount idx
00: 3fd5ef93af8e2b2c58656dd04a9e6208186bc9de20cd89c428c42d4dbd85aa58 467.556964665000 60202 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": 35673, "vin": [ { "gen": { "height": 35663 } } ], "vout": [ { "amount": 467556964665, "target": { "key": "3fd5ef93af8e2b2c58656dd04a9e6208186bc9de20cd89c428c42d4dbd85aa58" } } ], "extra": [ 1, 174, 42, 218, 250, 161, 38, 56, 154, 88, 156, 15, 14, 182, 19, 128, 216, 188, 1, 157, 71, 26, 130, 109, 242, 127, 131, 139, 157, 235, 191, 39, 86, 2, 17, 0, 0, 0, 1, 73, 67, 205, 159, 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