Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4e2883a8d7004004339b95d6a20b2171fd8e52c2291981d1d3b6d9d0a9d83cde

Tx prefix hash: 624b5643dd3b5f2305d5f469ee48c871d31b7849daf383b1bc1f3ad67ac76068
Tx public key: 543c81f369a673ed74cdec34a90c70c3bcf0412ca38a11beccc82b87062f3e09
Timestamp: 1577999034 Timestamp [UCT]: 2020-01-02 21:03:54 Age [y:d:h:m:s]: 04:361:21:51:14
Block: 37423 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1147771 RingCT/type: yes/0
Extra: 01543c81f369a673ed74cdec34a90c70c3bcf0412ca38a11beccc82b87062f3e090211000000178a2ee0d9000000000000000000

1 output(s) for total of 461.320673482000 dcy

stealth address amount amount idx
00: 55b283cc7781f5df3583eaeac07043c96c7c4a1baf811cbeca994d81dd493d11 461.320673482000 63523 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": 37433, "vin": [ { "gen": { "height": 37423 } } ], "vout": [ { "amount": 461320673482, "target": { "key": "55b283cc7781f5df3583eaeac07043c96c7c4a1baf811cbeca994d81dd493d11" } } ], "extra": [ 1, 84, 60, 129, 243, 105, 166, 115, 237, 116, 205, 236, 52, 169, 12, 112, 195, 188, 240, 65, 44, 163, 138, 17, 190, 204, 200, 43, 135, 6, 47, 62, 9, 2, 17, 0, 0, 0, 23, 138, 46, 224, 217, 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