← previous blocknext block →recent activity
Analyzing
Block #89,567,240
20 transactions · 19 stateful · 2026-07-23 04:37:21 UTC
Parallelism
90/100
Blocked
11%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #89,567,240 · 20 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w19w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x35080a86…ff19
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4886b3df…67a3
0x34b655…2a6f
4 touches
1 conflict
0xc1da8f73…484c
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x40970e69…da50
0x2b46c0…1669
2 touches
0 conflicts
0x8cf3d245…1d0d
0x2b46c0…1669
2 touches
0 conflicts
0xb05cd4f5…73d0
0x2b46c0…1669
2 touches
0 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
1 conflict on slot 0x35080a86a3…6aff19
Audit this contract →
← previous block·next block →recent activity