← previous blocknext block →recent activity
Analyzing
Block #89,709,792
11 transactions · 11 stateful · 2026-07-23 19:03:37 UTC
Parallelism
82/100
Blocked
18%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #89,709,792 · 11 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
1w05w16w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5146ef12…80c6
0x34b655…2a6f
4 touches
1 conflict
0x80656e3b…9240
0x34b655…2a6f
4 touches
1 conflict
0xb42ec1f0…8cbc
0x34b655…2a6f
4 touches
1 conflict
0xd6d040d9…9ae3
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0xffb2bfcf…b92a
0x34b655…2a6f
4 touches
1 conflict
0x1e56f6b6…5940
0x34b655…2a6f
2 touches
0 conflicts
0x2b8c5b87…0cac
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 0x5146ef1273…6d80c6
Audit this contract →
← previous block·next block →recent activity