← previous blocknext block →recent activity
Analyzing
Block #98,458,775
21 transactions · 19 stateful · 2026-08-23 10:47:20 UTC
Parallelism
76/100
Blocked
37%
Avg conflicts / tx
0.48
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,458,775 · 21 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w06w17w012w115w116w219w320w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xa7ecbbe7…f713
0x34b655…2a6f
6 touches
3 conflicts
0xec2a8d79…70cb
0x34b655…2a6f
6 touches
3 conflicts
0x42d5e8f3…5930
0x34b655…2a6f
4 touches
1 conflict
0xbb97db90…4c93
0xc8689a…ee79
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0x2cf00801…51b8
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
6 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity