← previous blocknext block →recent activity
Analyzing
Block #89,598,389
12 transactions · 11 stateful · 2026-07-23 08:05:20 UTC
Parallelism
83/100
Blocked
18%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #89,598,389 · 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
5w07w19w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfc4d32c0…39f9
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6426
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xf51ec09c…b4a9
0x34b655…2a6f
4 touches
1 conflict
0x091164f5…6e32
0x34b655…2a6f
4 touches
1 conflict
0x091164f5…6e33
0x34b655…2a6f
4 touches
1 conflict
0x266a6b2c…4376
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
1 conflict on slot 0xfc4d32c0b5…3239f9
Audit this contract →
← previous block·next block →recent activity