← previous blocknext block →recent activity
Analyzing
Block #89,683,197
8 transactions · 8 stateful · 2026-07-23 16:49:32 UTC
Parallelism
63/100
Blocked
25%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #89,683,197 · 8 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
5w06w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xd2e482cc…0a50
0x34b655…2a6f
4 touches
1 conflict
0x2a5e2b11…1c2b
0x34b655…2a6f
4 touches
1 conflict
0x9feb7f16…58ee
0x34b655…2a6f
3 touches
1 conflict
0x1c3295fd…097a
0x34b655…2a6f
2 touches
0 conflicts
0x1ffbc5c9…461f
0x34b655…2a6f
2 touches
0 conflicts
0x266a6b2c…4376
0x34b655…2a6f
2 touches
0 conflicts
0x266a6b2c…4377
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
3 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity