Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 06de0281a06ca4f558760149f5c2cf95d3269f21b8f90b7a4ee86ac8cb7d35d0

Tx prefix hash: 664dda09a2d607848dff6f1e2195d53fa674a9c5637f2f1650f800e44d80926e
Tx public key: 859c09835d64b9b3620d4a35383ae89d8a104c88dcb948ccecd7623783629221
Timestamp: 1583638508 Timestamp [UCT]: 2020-03-08 03:35:08 Age [y:d:h:m:s]: 05:005:12:23:37
Block: 78470 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1159325 RingCT/type: yes/0
Extra: 01859c09835d64b9b3620d4a35383ae89d8a104c88dcb948ccecd76237836292210211000000058e602c4c000000000000000000

1 output(s) for total of 337.285062444000 dcy

stealth address amount amount idx
00: f65bbb0ae4dd20c9109d3c263711a1ec11aae29fd295ba112aaf002a11dbdd42 337.285062444000 143926 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": 78480, "vin": [ { "gen": { "height": 78470 } } ], "vout": [ { "amount": 337285062444, "target": { "key": "f65bbb0ae4dd20c9109d3c263711a1ec11aae29fd295ba112aaf002a11dbdd42" } } ], "extra": [ 1, 133, 156, 9, 131, 93, 100, 185, 179, 98, 13, 74, 53, 56, 58, 232, 157, 138, 16, 76, 136, 220, 185, 72, 204, 236, 215, 98, 55, 131, 98, 146, 33, 2, 17, 0, 0, 0, 5, 142, 96, 44, 76, 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