Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8ba441feb79156a32f3bbd71b8054b18e2b73327d364cc04a530d3c4efcce5c6

Tx prefix hash: 390cc7cfd29213204e70d3108b13fc76dd9fca720a4c075821b7801da81eee50
Tx public key: 7fc2ec77e4f8e51c491e66d5e4e5056ac1aa7ff10e73665f8c77b888779899f4
Timestamp: 1708609011 Timestamp [UCT]: 2024-02-22 13:36:51 Age [y:d:h:m:s]: 01:270:09:37:46
Block: 963115 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 452010 RingCT/type: yes/0
Extra: 017fc2ec77e4f8e51c491e66d5e4e5056ac1aa7ff10e73665f8c77b888779899f40211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 94536c43ef4b7f93db13eb07c37a1bc4927fcfe93ff9788c9e23be0c0532a3c5 0.600000000000 1422814 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": 963125, "vin": [ { "gen": { "height": 963115 } } ], "vout": [ { "amount": 600000000, "target": { "key": "94536c43ef4b7f93db13eb07c37a1bc4927fcfe93ff9788c9e23be0c0532a3c5" } } ], "extra": [ 1, 127, 194, 236, 119, 228, 248, 229, 28, 73, 30, 102, 213, 228, 229, 5, 106, 193, 170, 127, 241, 14, 115, 102, 95, 140, 119, 184, 136, 119, 152, 153, 244, 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