← previous blocknext block →recent activity
Analyzing
Block #96,262,765
6 transactions · 5 stateful · 2026-08-15 17:26:25 UTC
Parallelism
67/100
Blocked
20%
Avg conflicts / tx
0.33
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,262,765 · 6 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
2w03w04w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7d3e3b93…b8eb
0x34b655…2a6f
4 touches
1 conflict
0x9b2d3bee…8eeb
0x34b655…2a6f
4 touches
1 conflict
0x9b2d3bee…8eec
0x34b655…2a6f
4 touches
1 conflict
0xea1b8c07…b969
0x34b655…2a6f
4 touches
1 conflict
0x1450f862…235e
0x34b655…2a6f
2 touches
0 conflicts
0x1bdb47ec…864a
0x34b655…2a6f
2 touches
0 conflicts
0x1bdb47ec…864b
0x34b655…2a6f
2 touches
0 conflicts
0x26607bc2…7fd6
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 0x7d3e3b9343…c9b8eb
Audit this contract →
← previous block·next block →recent activity