← previous blocknext block →recent activity
Analyzing
Block #97,684,850
20 transactions · 18 stateful · 2026-08-20 17:36:02 UTC
Parallelism
70/100
Blocked
44%
Avg conflicts / tx
0.6
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #97,684,850 · 20 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
1w02w03w16w17w29w210w311w318w419w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x9c5fcee3…028c
0x34b655…2a6f
6 touches
3 conflicts
0xe41626f9…dd93
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x230f6b52…4531
0x34b655…2a6f
4 touches
1 conflict
0x243344bd…0b8c
0x34b655…2a6f
4 touches
1 conflict
0x2b69cc9b…2aca
0x34b655…2a6f
4 touches
1 conflict
0x2ed00f98…da9f
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity