← previous blocknext block →recent activity
Analyzing
Block #89,844,002
9 transactions · 7 stateful · 2026-07-24 06:21:10 UTC
Parallelism
78/100
Blocked
14%
Avg conflicts / tx
0.22
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #89,844,002 · 9 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
4w07w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x680fdd59…e84d
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x0f2d78b1…7363
0x34b655…2a6f
4 touches
1 conflict
0xaf54a4a7…3467
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x304a552a…8fc7
0x34b655…2a6f
2 touches
0 conflicts
0x304a552a…8fc8
0x34b655…2a6f
2 touches
0 conflicts
0x3df0422c…fd38
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 0x680fdd5929…bce84d
Audit this contract →
← previous block·next block →recent activity