← previous blocknext block →recent activity
Analyzing
Block #98,499,603
21 transactions · 21 stateful · 2026-08-23 14:13:04 UTC
Parallelism
71/100
Blocked
48%
Avg conflicts / tx
0.9
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #98,499,603 · 21 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w06w18w212w313w414w215w116w517w018w120w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x627738d1…db02
0x34b655…2a6f
8 touches
6 conflicts
0x094587ac…7106
0x34b655…2a6f
8 touches
6 conflicts
0x76622fb2…4f08
0x34b655…2a6f
6 touches
3 conflicts
0xee757899…302b
0x34b655…2a6f
6 touches
3 conflicts
0xaf86cd8e…83d2
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x991ec4e9…67c2
0x34b655…2a6f
6 touches
3 conflicts
0xa3644f89…29eb
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0x627738d150…b6db02
Audit this contract →
← previous block·next block →recent activity