Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2efeef09c4829186a475b34839d4deb62ae2fc630e9f5fb647220623d7dd4598

Tx prefix hash: 3ba4ba3d8539c7e9c0f6c83430362a56397c98994b91e504be8cfc18833ee800
Tx public key: 68e56b7a35537838bde98ec6ce4fb813c3774f7e334f47a63fcdbc8edd6fe357
Timestamp: 1579202496 Timestamp [UCT]: 2020-01-16 19:21:36 Age [y:d:h:m:s]: 04:347:05:29:00
Block: 47041 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1137608 RingCT/type: yes/0
Extra: 0168e56b7a35537838bde98ec6ce4fb813c3774f7e334f47a63fcdbc8edd6fe3570211000000054943cd9f000000000000000000

1 output(s) for total of 428.681238411000 dcy

stealth address amount amount idx
00: 831f06ac1e53a18bbf2fbd885d08438c6f823bc771f0286ac4fa15197e8cbb4a 428.681238411000 86849 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": 47051, "vin": [ { "gen": { "height": 47041 } } ], "vout": [ { "amount": 428681238411, "target": { "key": "831f06ac1e53a18bbf2fbd885d08438c6f823bc771f0286ac4fa15197e8cbb4a" } } ], "extra": [ 1, 104, 229, 107, 122, 53, 83, 120, 56, 189, 233, 142, 198, 206, 79, 184, 19, 195, 119, 79, 126, 51, 79, 71, 166, 63, 205, 188, 142, 221, 111, 227, 87, 2, 17, 0, 0, 0, 5, 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