Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bd64f0cacdbe1fa4b6f8f2a9e7cfa116678f74811a75d08e019b0280df391774

Tx prefix hash: 6d46ab7f07d098a0e0ad830c3e48864cbbcd6ccd391963008db814202dbc1192
Tx public key: 2de68f77e6205084dbdc6679e5b3a9773291e5ea0aef40195e0d150419003dc7
Timestamp: 1739262134 Timestamp [UCT]: 2025-02-11 08:22:14 Age [y:d:h:m:s]: 00:353:17:46:43
Block: 1216808 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 250494 RingCT/type: yes/0
Extra: 012de68f77e6205084dbdc6679e5b3a9773291e5ea0aef40195e0d150419003dc70211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b169671323a34c71702d79ddc60103e639f108fb0b3acc7aaf54b73a73b68b8c 0.600000000000 1703615 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": 1216818, "vin": [ { "gen": { "height": 1216808 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b169671323a34c71702d79ddc60103e639f108fb0b3acc7aaf54b73a73b68b8c" } } ], "extra": [ 1, 45, 230, 143, 119, 230, 32, 80, 132, 219, 220, 102, 121, 229, 179, 169, 119, 50, 145, 229, 234, 10, 239, 64, 25, 94, 13, 21, 4, 25, 0, 61, 199, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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