← previous blocknext block →recent activity
Analyzing
Block #89,693,304
18 transactions · 17 stateful · 2026-07-23 17:40:31 UTC
Parallelism
83/100
Blocked
35%
Avg conflicts / tx
0.39
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #89,693,304 · 18 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w05w06w19w111w114w215w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x37c70870…b872
0x34b655…2a6f
4 touches
1 conflict
0x53b4ef2b…8a05
0x34b655…2a6f
4 touches
1 conflict
0x5ea9eca9…22a6
0x34b655…2a6f
4 touches
1 conflict
0x5ea9eca9…22a7
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x85d21fba…c8b2
0x34b655…2a6f
4 touches
1 conflict
0x96d4f560…c558
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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity