Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a86969eeb65295b3ea9058f6dc5d17d5252822e0bbdc0f43a27e4195616dd298

Tx prefix hash: 223d1801f0637b8544b398182f9a5bc3fd02846ad393e997676826a94f8eaade
Tx public key: 3140b84e6dc4a82a1e715746a249d09a70f00730d0f12fe889c73817a6d69b89
Timestamp: 1707362430 Timestamp [UCT]: 2024-02-08 03:20:30 Age [y:d:h:m:s]: 01:062:05:13:46
Block: 952771 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 305528 RingCT/type: yes/0
Extra: 013140b84e6dc4a82a1e715746a249d09a70f00730d0f12fe889c73817a6d69b8902110000000752d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0910517237cd1c33edc9baaa5eeb680c74469e62cc9c78564939ed6af4a12eaf 0.600000000000 1411901 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": 952781, "vin": [ { "gen": { "height": 952771 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0910517237cd1c33edc9baaa5eeb680c74469e62cc9c78564939ed6af4a12eaf" } } ], "extra": [ 1, 49, 64, 184, 78, 109, 196, 168, 42, 30, 113, 87, 70, 162, 73, 208, 154, 112, 240, 7, 48, 208, 241, 47, 232, 137, 199, 56, 23, 166, 214, 155, 137, 2, 17, 0, 0, 0, 7, 82, 212, 126, 148, 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