← previous blocknext block →recent activity
Analyzing
Block #96,542,964
8 transactions · 7 stateful · 2026-08-16 16:55:59 UTC
Parallelism
75/100
Blocked
14%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,542,964 · 8 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcc1b52d3…76b9
0x34b655…2a6f
4 touches
1 conflict
0xd18e4cb7…88d4
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0fb9e50c…1a35
0x34b655…2a6f
2 touches
0 conflicts
0x41bfea99…ac66
0x34b655…2a6f
2 touches
0 conflicts
0x745a7fd6…5fea
0x34b655…2a6f
2 touches
0 conflicts
0x8fa0bb19…bfed
0x34b655…2a6f
2 touches
0 conflicts
0x91b0f8ed…6bd6
0x34b655…2a6f
2 touches
0 conflicts
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
1 conflict on slot 0xcc1b52d315…6576b9
Audit this contract →
← previous block·next block →recent activity