← previous blocknext block →recent activity
Analyzing
Block #96,826,594
8 transactions · 7 stateful · 2026-08-17 16:42:33 UTC
Parallelism
75/100
Blocked
14%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,826,594 · 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
2w03w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x91b0f8ed…6bd7
0x34b655…2a6f
4 touches
1 conflict
0x91b0f8ed…6bd6
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x0487d7b3…f375
0x34b655…2a6f
2 touches
0 conflicts
0x06a2f8c9…6b20
0x34b655…2a6f
2 touches
0 conflicts
0x06df379f…2653
0x34b655…2a6f
2 touches
0 conflicts
0x2b8d9898…d525
0x34b655…2a6f
2 touches
0 conflicts
0x308e9846…844c
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 0x91b0f8edc5…b76bd7
Audit this contract →
← previous block·next block →recent activity