Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b2c4e77c184671a7977dd3f51d875f21ebc03717094170fc770a38023aaa1553

Tx prefix hash: 0f80392c79505e71a9653a165f718bba7464b0559c7a660339e3c28aaece8e7c
Tx public key: 079e06fcae2091247ec12e6601c74617d5dd20df8c3ce728b2fe3fe419b34b8c
Timestamp: 1575875657 Timestamp [UCT]: 2019-12-09 07:14:17 Age [y:d:h:m:s]: 04:353:11:34:39
Block: 23676 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1137916 RingCT/type: yes/0
Extra: 01079e06fcae2091247ec12e6601c74617d5dd20df8c3ce728b2fe3fe419b34b8c0211000000169159db1e000000000000000000

1 output(s) for total of 512.333147408000 dcy

stealth address amount amount idx
00: 05ad82fc5ca9924f503a1fbd42ab11ec438928319abc80264ea8a93ad9d3e3a4 512.333147408000 38405 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": 23686, "vin": [ { "gen": { "height": 23676 } } ], "vout": [ { "amount": 512333147408, "target": { "key": "05ad82fc5ca9924f503a1fbd42ab11ec438928319abc80264ea8a93ad9d3e3a4" } } ], "extra": [ 1, 7, 158, 6, 252, 174, 32, 145, 36, 126, 193, 46, 102, 1, 199, 70, 23, 213, 221, 32, 223, 140, 60, 231, 40, 178, 254, 63, 228, 25, 179, 75, 140, 2, 17, 0, 0, 0, 22, 145, 89, 219, 30, 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