← previous blocknext block →recent activity
Analyzing
Block #89,556,091
12 transactions · 12 stateful · 2026-07-23 03:22:52 UTC
Parallelism
83/100
Blocked
8%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #89,556,091 · 12 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
6w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7ba216b2…eec2
0x34b655…2a6f
4 touches
1 conflict
0x8881815c…5b40
0x34b655…2a6f
4 touches
1 conflict
0x9a9eea06…1cfa
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xfeed0fe5…aabb
0x34b655…2a6f
4 touches
1 conflict
0x10af5537…5a9a
0x34b655…2a6f
4 touches
1 conflict
0x7ba216b2…eec1
0x34b655…2a6f
4 touches
1 conflict
0xb14a1ff1…42f9
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 0x7ba216b264…52eec2
Audit this contract →
← previous block·next block →recent activity