Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1fce851ccc37dc1062b11eb24a646c71ad77dc800b37e14b07e32535b4e0dc83

Tx prefix hash: 75c315a4a6b38350d2def8ab32519f1dae580a622be3f137974a468c3ad3be4f
Tx public key: 8c66cf5676002978bbbc0f07a4b184eebd99f01d8bb80bb54bfa1c7ff33c94a4
Timestamp: 1581705009 Timestamp [UCT]: 2020-02-14 18:30:09 Age [y:d:h:m:s]: 05:007:19:58:24
Block: 65318 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1158090 RingCT/type: yes/0
Extra: 018c66cf5676002978bbbc0f07a4b184eebd99f01d8bb80bb54bfa1c7ff33c94a4021100000002026b59f3000000000000000000

1 output(s) for total of 372.885213230000 dcy

stealth address amount amount idx
00: 57748809971ac04a44f37e93026f15bc99b5e13801304243cf426cf15ff793f8 372.885213230000 120363 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": 65328, "vin": [ { "gen": { "height": 65318 } } ], "vout": [ { "amount": 372885213230, "target": { "key": "57748809971ac04a44f37e93026f15bc99b5e13801304243cf426cf15ff793f8" } } ], "extra": [ 1, 140, 102, 207, 86, 118, 0, 41, 120, 187, 188, 15, 7, 164, 177, 132, 238, 189, 153, 240, 29, 139, 184, 11, 181, 75, 250, 28, 127, 243, 60, 148, 164, 2, 17, 0, 0, 0, 2, 2, 107, 89, 243, 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