← previous blocknext block →recent activity
Analyzing
Block #96,436,085
17 transactions · 16 stateful · 2026-08-16 07:58:07 UTC
Parallelism
53/100
Blocked
63%
Avg conflicts / tx
1.65
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #96,436,085 · 17 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w16w27w38w49w515w616w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x53f393fa…00b9
0x34b655…2a6f
12 touches
15 conflicts
0xca841faa…486a
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x0d488000…3831
0x34b655…2a6f
6 touches
3 conflicts
0xf5559a5b…ef74
0x34b655…2a6f
4 touches
1 conflict
0x32287d4a…6699
0x34b655…2a6f
4 touches
1 conflict
0xc2db6e7a…d074
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
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
15 conflicts on slot 0x53f393fafd…2a00b9
Audit this contract →
← previous block·next block →recent activity