← previous blocknext block →recent activity
Analyzing
Block #98,948,242
18 transactions · 15 stateful · 2026-08-25 04:26:12 UTC
Parallelism
72/100
Blocked
47%
Avg conflicts / tx
0.56
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,948,242 · 18 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
1w02w03w06w18w110w111w013w214w315w117w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xd2b8323f…f51a
0x065c9d…c394
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x0ec109d3…9cd0
0x34b655…2a6f
4 touches
1 conflict
0x110dd6cf…4f2d
0x34b655…2a6f
4 touches
1 conflict
0x33f12650…b80b
0x34b655…2a6f
4 touches
1 conflict
0x33f12650…b80c
0x34b655…2a6f
4 touches
1 conflict
0x36918c55…8424
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 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity