← previous blocknext block →recent activity
Analyzing
Block #88,082,744
23 transactions · 21 stateful · 2026-07-16 07:09:21 UTC
Parallelism
70/100
Blocked
48%
Avg conflicts / tx
1.17
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #88,082,744 · 23 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
1w02w13w26w08w19w210w314w215w316w421w522w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0dd44476…ef40
0x34b655…2a6f
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x4ae7987e…d091
0x34b655…2a6f
6 touches
3 conflicts
0x78346476…4311
0x34b655…2a6f
6 touches
3 conflicts
0x79277877…6098
0x34b655…2a6f
6 touches
3 conflicts
0x7ab016af…dae9
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 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
15 conflicts on slot 0x0dd44476b8…7fef40
Audit this contract →
← previous block·next block →recent activity