← previous blocknext block →recent activity
Analyzing
Block #89,830,018
9 transactions · 9 stateful · 2026-07-24 05:10:34 UTC
Parallelism
78/100
Blocked
11%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #89,830,018 · 9 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
5w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0f69f34e…c78e
0x34b655…2a6f
4 touches
1 conflict
0xe8b7850a…65d0
0x34b655…2a6f
4 touches
1 conflict
0xfc0e8d5c…cfe6
0x34b655…2a6f
4 touches
1 conflict
0xe3fbd09c…9f30
0x34b655…2a6f
4 touches
1 conflict
0x70b7b52e…7743
0x34b655…2a6f
4 touches
1 conflict
0x70b7b52e…7744
0x34b655…2a6f
4 touches
1 conflict
0x1f1b0220…4fdf
0x34b655…2a6f
3 touches
1 conflict
0x53ca1284…cb2c
0x34b655…2a6f
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 0x0f69f34ef2…4bc78e
Audit this contract →
← previous block·next block →recent activity