← previous blocknext block →recent activity
Analyzing
Block #89,881,835
11 transactions · 9 stateful · 2026-07-24 09:31:29 UTC
Parallelism
64/100
Blocked
33%
Avg conflicts / tx
0.27
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #89,881,835 · 11 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w19w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x59991669…58c6
0x34b655…2a6f
4 touches
1 conflict
0x81561f70…fefd
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xeb0ed9c8…5f39
0x34b655…2a6f
4 touches
1 conflict
0x55eef346…d185
0x34b655…2a6f
4 touches
1 conflict
0x920da1e1…0d64
0x065c9d…c394
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 0x59991669d4…0858c6
Audit this contract →
← previous block·next block →recent activity