← previous blocknext block →recent activity
Analyzing
Block #98,445,162
18 transactions · 16 stateful · 2026-08-23 09:38:39 UTC
Parallelism
89/100
Blocked
13%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #98,445,162 · 18 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
3w04w112w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf85bdc12…5dff
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x647d8832…1676
0x34b655…2a6f
4 touches
1 conflict
0x213ee207…a151
0x2b46c0…1669
2 touches
0 conflicts
0x46279ae7…20dd
0x2b46c0…1669
2 touches
0 conflicts
0x2ad2f4bc…1800
0x34b655…2a6f
2 touches
0 conflicts
0x450f5a60…bf64
0x34b655…2a6f
2 touches
0 conflicts
0x5af10b50…8d5c
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 0xf85bdc12e0…265dff
Audit this contract →
← previous block·next block →recent activity