Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cbb984c748068ef8829787340042be2bcdcc5caeb4c3ca909f2b55f3dcf79f97

Tx prefix hash: 011a16af359d624dca905b339688e9a6e2dc36962d6faed41653f6932674b7e2
Tx public key: f788e950040f95f8003ea8a8852006e2ef2db69d6fad93cea0f46720d80e3d89
Timestamp: 1719552765 Timestamp [UCT]: 2024-06-28 05:32:45 Age [y:d:h:m:s]: 01:134:14:08:08
Block: 1053846 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 354737 RingCT/type: yes/0
Extra: 01f788e950040f95f8003ea8a8852006e2ef2db69d6fad93cea0f46720d80e3d890211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8c2f5bc7f8f43efa922dd0f7414d9efe9f67e7b8a513913feadaade50cad3ba8 0.600000000000 1524197 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": 1053856, "vin": [ { "gen": { "height": 1053846 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8c2f5bc7f8f43efa922dd0f7414d9efe9f67e7b8a513913feadaade50cad3ba8" } } ], "extra": [ 1, 247, 136, 233, 80, 4, 15, 149, 248, 0, 62, 168, 168, 133, 32, 6, 226, 239, 45, 182, 157, 111, 173, 147, 206, 160, 244, 103, 32, 216, 14, 61, 137, 2, 17, 0, 0, 0, 5, 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