Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4373b9dae3cbf5178c6ed09cdd4b9830bb6c285605ad1745d218463851b8711e

Tx prefix hash: 1c12f0d8f014930b2e4a4c47e5e7f731bcbebe20394b19aac70492d5067218d3
Tx public key: 4e16b2cdb1dd35b61addaae9d7d70e7bb86b27de000541eb3eb1f4d603fe5756
Timestamp: 1704412722 Timestamp [UCT]: 2024-01-04 23:58:42 Age [y:d:h:m:s]: 01:166:17:55:25
Block: 928313 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 380206 RingCT/type: yes/0
Extra: 014e16b2cdb1dd35b61addaae9d7d70e7bb86b27de000541eb3eb1f4d603fe575602110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bfb8c59cd9533de8f6546309970978d594943d5a861e337a7a27c7bb38bab22f 0.600000000000 1386171 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": 928323, "vin": [ { "gen": { "height": 928313 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bfb8c59cd9533de8f6546309970978d594943d5a861e337a7a27c7bb38bab22f" } } ], "extra": [ 1, 78, 22, 178, 205, 177, 221, 53, 182, 26, 221, 170, 233, 215, 215, 14, 123, 184, 107, 39, 222, 0, 5, 65, 235, 62, 177, 244, 214, 3, 254, 87, 86, 2, 17, 0, 0, 0, 7, 89, 218, 211, 245, 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