← previous blocknext block →recent activity
Analyzing
Block #88,089,912
21 transactions · 20 stateful · 2026-07-16 07:57:18 UTC
Parallelism
67/100
Blocked
35%
Avg conflicts / tx
0.76
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #88,089,912 · 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
1w05w06w18w09w213w116w317w418w519w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5777bd87…71bd
0x34b655…2a6f
8 touches
6 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x7aad02c6…b979
0x34b655…2a6f
6 touches
3 conflicts
0xa1ff0729…0146
0xa6afd3…d132
4 touches
1 conflict
0x17e8055c…3415
0x34b655…2a6f
4 touches
1 conflict
0xbb4fd99a…afa6
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
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 0x5777bd874f…7071bd
Audit this contract →
← previous block·next block →recent activity