← previous blocknext block →recent activity
Analyzing
Block #98,848,669
14 transactions · 14 stateful · 2026-08-24 20:05:17 UTC
Parallelism
57/100
Blocked
36%
Avg conflicts / tx
0.79
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #98,848,669 · 14 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
2w04w16w08w29w311w012w413w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x731d7308…fd26
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x0befa473…81b3
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0xbbb93c5b…db1b
0x34b655…2a6f
5 touches
3 conflicts
0x699ee60f…de01
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 0x731d73081c…7dfd26
Audit this contract →
← previous block·next block →recent activity