← previous blocknext block →recent activity
Analyzing
Block #98,086,475
23 transactions · 21 stateful · 2026-08-22 03:33:20 UTC
Parallelism
83/100
Blocked
48%
Avg conflicts / tx
0.65
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,086,475 · 23 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w04w15w06w17w28w09w115w216w017w119w120w221w322w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x53eac009…b61b
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0xbde524f4…43bf
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xf88ccd07…a684
0xa6afd3…d132
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x62910921…3016
0x34b655…2a6f
4 touches
1 conflict
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 0x53eac00933…f3b61b
Audit this contract →
← previous block·next block →recent activity