Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0b024ccb027894fa921bf74d79f3e5e4db60dcdc86ba2251c3fe0eb2c381ced4

Tx prefix hash: 85130516fce73dc1935fc14f846dd68c7fd407e5c58bdcc456eb4f0c422cd93e
Tx public key: bf93db08c17fca1bd9ac9d38ad592b7e66241a94b1986ddad13ee14b822e2608
Timestamp: 1698296374 Timestamp [UCT]: 2023-10-26 04:59:34 Age [y:d:h:m:s]: 01:189:05:58:14
Block: 877839 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 396269 RingCT/type: yes/0
Extra: 01bf93db08c17fca1bd9ac9d38ad592b7e66241a94b1986ddad13ee14b822e26080211000000064b8f5122000000000000000000

1 output(s) for total of 0.757451797000 dcy

stealth address amount amount idx
00: f0091ec8a062b3ae6c0e1986d3b710ba552e17f213ab7f93e649e05d20ef8b1f 0.757451797000 1333231 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": 877849, "vin": [ { "gen": { "height": 877839 } } ], "vout": [ { "amount": 757451797, "target": { "key": "f0091ec8a062b3ae6c0e1986d3b710ba552e17f213ab7f93e649e05d20ef8b1f" } } ], "extra": [ 1, 191, 147, 219, 8, 193, 127, 202, 27, 217, 172, 157, 56, 173, 89, 43, 126, 102, 36, 26, 148, 177, 152, 109, 218, 209, 62, 225, 75, 130, 46, 38, 8, 2, 17, 0, 0, 0, 6, 75, 143, 81, 34, 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