← previous blocknext block →recent activity
Analyzing
Block #98,102,663
23 transactions · 23 stateful · 2026-08-22 04:54:48 UTC
Parallelism
83/100
Blocked
39%
Avg conflicts / tx
0.52
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,102,663 · 23 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w07w08w19w010w111w112w214w115w016w120w221w322w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x62910921…3016
0x34b655…2a6f
6 touches
3 conflicts
0xcac95629…6322
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xd17580f9…ece1
0x754704…b603
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xcf11cf1a…ec04
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
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 0x629109215a…273016
Audit this contract →
← previous block·next block →recent activity