← previous blocknext block →recent activity
Analyzing
Block #88,366,556
23 transactions · 20 stateful · 2026-07-17 14:49:11 UTC
Parallelism
74/100
Blocked
45%
Avg conflicts / tx
0.52
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #88,366,556 · 23 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w05w06w17w28w39w413w115w116w417w521w022w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa55c4598…2988
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x160f117d…8e90
0x065c9d…c394
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4d537c35…b570
0x34b655…2a6f
4 touches
1 conflict
0x547ab6de…28d1
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
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
3 conflicts on slot 0xa55c45989b…e52988
Audit this contract →
← previous block·next block →recent activity