← previous blocknext block →recent activity
Analyzing
Block #89,588,110
13 transactions · 11 stateful · 2026-07-23 06:56:40 UTC
Parallelism
85/100
Blocked
9%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #89,588,110 · 13 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
6w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x091164f5…6e32
0x34b655…2a6f
4 touches
1 conflict
0x091164f5…6e33
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x9f4bc324…e6a6
0x34b655…2a6f
4 touches
1 conflict
0xabf57eb6…416d
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xf4528b84…e78a
0x34b655…2a6f
4 touches
1 conflict
0xf8439e49…d9c1
0x34b655…2a6f
3 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 0x091164f59d…fd6e32
Audit this contract →
← previous block·next block →recent activity