← previous blocknext block →recent activity
Analyzing
Block #95,903,213
25 transactions · 18 stateful · 2026-08-14 11:17:38 UTC
Parallelism
84/100
Blocked
44%
Avg conflicts / tx
0.52
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #95,903,213 · 25 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w110w011w212w113w321w022w123w224w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbd0f7e08…440a
0x34b655…2a6f
6 touches
3 conflicts
0x8a5ced1c…3b29
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0018
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0028
0x1b6862…e19c
4 touches
1 conflict
0xada193dc…5c79
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: Perpl
3 conflicts on slot 0xbd0f7e0862…5b440a
Audit this contract →
← previous block·next block →recent activity