← previous blocknext block →recent activity
Analyzing
Block #89,852,991
11 transactions · 10 stateful · 2026-07-24 07:06:24 UTC
Parallelism
82/100
Blocked
20%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #89,852,991 · 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
1w02w14w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5e3014f0…b4e1
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x32e4c206…a476
0x34b655…2a6f
4 touches
1 conflict
0x01076862…1db7
0x34b655…2a6f
2 touches
0 conflicts
0x0147158c…f0a8
0x34b655…2a6f
2 touches
0 conflicts
0x08330b36…ae29
0x34b655…2a6f
2 touches
0 conflicts
0x1b5d2e60…99b5
0x34b655…2a6f
2 touches
0 conflicts
0x2697123c…8526
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 0x5e3014f0c7…b1b4e1
Audit this contract →
← previous block·next block →recent activity