← previous blocknext block →recent activity
Analyzing
Block #88,191,310
21 transactions · 18 stateful · 2026-07-16 19:16:26 UTC
Parallelism
67/100
Blocked
61%
Avg conflicts / tx
1.29
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #88,191,310 · 21 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w38w09w010w411w212w113w116w317w418w520w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0x4cabb80a…46bf
0x34b655…2a6f
8 touches
6 conflicts
0xa3a621f8…75a2
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xed10a777…0ca7
0x34b655…2a6f
6 touches
3 conflicts
0x59037442…7fd5
0x34b655…2a6f
6 touches
3 conflicts
0x9001f549…089d
0x34b655…2a6f
4 touches
1 conflict
0x96d5741f…c52d
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
10 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity