← previous blocknext block →recent activity
Analyzing
Block #89,857,322
12 transactions · 12 stateful · 2026-07-24 07:28:11 UTC
Parallelism
75/100
Blocked
17%
Avg conflicts / tx
0.25
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #89,857,322 · 12 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
6w07w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x68a9868a…6c27
0x34b655…2a6f
6 touches
3 conflicts
0x67a56c8b…f955
0x34b655…2a6f
6 touches
3 conflicts
0xa46242d8…c0a7
0x34b655…2a6f
4 touches
1 conflict
0xa46242d8…c0a8
0x34b655…2a6f
4 touches
1 conflict
0x7c51d9aa…af39
0x34b655…2a6f
4 touches
1 conflict
0xba333668…3079
0x34b655…2a6f
3 touches
1 conflict
0xb57b4bde…7af3
0x34b655…2a6f
3 touches
1 conflict
0x08d53462…97ef
0x2b46c0…1669
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 0x68a9868ad9…5d6c27
Audit this contract →
← previous block·next block →recent activity