← previous blocknext block →recent activity
Analyzing
Block #96,293,496
14 transactions · 13 stateful · 2026-08-15 20:00:59 UTC
Parallelism
64/100
Blocked
62%
Avg conflicts / tx
1.07
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #96,293,496 · 14 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w05w16w18w29w210w211w212w313w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x86c98782…f3b7
0x34b655…2a6f
10 touches
10 conflicts
0xe999cbf5…d18a
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x5ec23a95…74a4
0x34b655…2a6f
4 touches
1 conflict
0x6f1a10f8…5a04
0x34b655…2a6f
4 touches
1 conflict
0x733a5000…6e67
0x34b655…2a6f
4 touches
1 conflict
0x827557c1…a6be
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
10 conflicts on slot 0x86c98782f1…e7f3b7
Audit this contract →
← previous block·next block →recent activity