← previous blocknext block →recent activity
Analyzing
Block #89,588,123
13 transactions · 11 stateful · 2026-07-23 06:56:46 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,123 · 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
4w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0b00aeff…7bd3
0x34b655…2a6f
4 touches
1 conflict
0x9de538e5…7632
0x34b655…2a6f
4 touches
1 conflict
0x9de538e5…7633
0x34b655…2a6f
4 touches
1 conflict
0x004f611b…5f47
0x34b655…2a6f
2 touches
0 conflicts
0x091164f5…6e32
0x34b655…2a6f
2 touches
0 conflicts
0x091164f5…6e33
0x34b655…2a6f
2 touches
0 conflicts
0x12b73161…a4ad
0x34b655…2a6f
2 touches
0 conflicts
0x2b11f1d9…3c8d
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 0x0b00aeff3e…077bd3
Audit this contract →
← previous block·next block →recent activity