← previous blocknext block →recent activity
Analyzing
Block #96,278,290
10 transactions · 9 stateful · 2026-08-15 18:44:31 UTC
Parallelism
50/100
Blocked
56%
Avg conflicts / tx
1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #96,278,290 · 10 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
1w02w14w15w26w37w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x49ffd065…33d1
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x4e58f1d6…2fca
0x34b655…2a6f
6 touches
3 conflicts
0x53a854a3…8db8
0x34b655…2a6f
4 touches
1 conflict
0x578347c5…cb6e
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x81561f70…fefd
0x34b655…2a6f
4 touches
1 conflict
0x818e1296…f4d7
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
6 conflicts on slot 0x49ffd065b3…cd33d1
Audit this contract →
← previous block·next block →recent activity