← previous blocknext block →recent activity
Analyzing
Block #98,848,269
26 transactions · 25 stateful · 2026-08-24 20:03:16 UTC
Parallelism
88/100
Blocked
28%
Avg conflicts / tx
0.31
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #98,848,269 · 26 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w16w07w18w09w110w217w019w122w123w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4af638b5…fdfd
0x34b655…2a6f
6 touches
3 conflicts
0x768cffcd…2648
0x34b655…2a6f
6 touches
3 conflicts
0x0eac6378…36f4
0x34b655…2a6f
6 touches
3 conflicts
0x41335ddf…94b9
0x34b655…2a6f
4 touches
1 conflict
0x454cdf57…aebc
0x34b655…2a6f
4 touches
1 conflict
0x68292fe7…d918
0x34b655…2a6f
4 touches
1 conflict
0x7251ce71…f35b
0x34b655…2a6f
4 touches
1 conflict
0x85a88798…f85e
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 0x4af638b566…c6fdfd
Audit this contract →
← previous block·next block →recent activity