Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a87cea88c02e5151249226ee7c677294912a0a5595072d3906eca2e09cca6a65

Tx prefix hash: 5a3652a3da545b5c67af02dd19379fdbe7766fe27231569fab7681e89e6d54d3
Tx public key: 1b32ef7e679ce1b0e8943929a4271cf502b1d1272e40158ec6cb88de52bfa4f8
Timestamp: 1617075992 Timestamp [UCT]: 2021-03-30 03:46:32 Age [y:d:h:m:s]: 03:274:02:45:40
Block: 229439 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 955393 RingCT/type: yes/0
Extra: 011b32ef7e679ce1b0e8943929a4271cf502b1d1272e40158ec6cb88de52bfa4f802110000006a90ec05ad000000000000000000

1 output(s) for total of 106.607805587000 dcy

stealth address amount amount idx
00: 21446df764b5f4a474d6366a04f97d2717d08a88a93e6fa835f97a9cbe7f9a2b 106.607805587000 476057 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": 229449, "vin": [ { "gen": { "height": 229439 } } ], "vout": [ { "amount": 106607805587, "target": { "key": "21446df764b5f4a474d6366a04f97d2717d08a88a93e6fa835f97a9cbe7f9a2b" } } ], "extra": [ 1, 27, 50, 239, 126, 103, 156, 225, 176, 232, 148, 57, 41, 164, 39, 28, 245, 2, 177, 209, 39, 46, 64, 21, 142, 198, 203, 136, 222, 82, 191, 164, 248, 2, 17, 0, 0, 0, 106, 144, 236, 5, 173, 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