Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1eafd7afea579d59cef70be8a9ba1a37bdcd166c556b6147cd816a6c2c1c4568

Tx prefix hash: 85ce89dc993da1cb2e06e9408b94d752437df28901e2094dd1c1fa751ed6b385
Tx public key: 4ab6a85f10e177f8ffd2ae955e6e113b53060d564726d44109cff2370dd7d045
Timestamp: 1704010626 Timestamp [UCT]: 2023-12-31 08:17:06 Age [y:d:h:m:s]: 01:311:16:45:13
Block: 924988 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 481594 RingCT/type: yes/0
Extra: 014ab6a85f10e177f8ffd2ae955e6e113b53060d564726d44109cff2370dd7d0450211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f77807d25d0a917e79f2521779d863557e5099fff6721e198cb5abd6c495024d 0.600000000000 1382748 of 15

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": 924998, "vin": [ { "gen": { "height": 924988 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f77807d25d0a917e79f2521779d863557e5099fff6721e198cb5abd6c495024d" } } ], "extra": [ 1, 74, 182, 168, 95, 16, 225, 119, 248, 255, 210, 174, 149, 94, 110, 17, 59, 83, 6, 13, 86, 71, 38, 212, 65, 9, 207, 242, 55, 13, 215, 208, 69, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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