← previous blocknext block →recent activity
Analyzing
Block #89,566,750
20 transactions · 18 stateful · 2026-07-23 04:34:04 UTC
Parallelism
75/100
Blocked
28%
Avg conflicts / tx
0.4
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #89,566,750 · 20 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w17w210w011w012w114w315w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x2b8d9898…d525
0x34b655…2a6f
5 touches
3 conflicts
0x2bac71c3…3296
0x34b655…2a6f
4 touches
1 conflict
0x2e089e16…3614
0x34b655…2a6f
4 touches
1 conflict
0x4ca81ae8…01d4
0x34b655…2a6f
4 touches
1 conflict
0x4de6ee0e…7fb4
0x34b655…2a6f
4 touches
1 conflict
0x65e36646…1715
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 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity