← previous blocknext block →recent activity
Analyzing
Block #98,060,103
18 transactions · 17 stateful · 2026-08-22 01:20:38 UTC
Parallelism
78/100
Blocked
29%
Avg conflicts / tx
0.33
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,060,103 · 18 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
1w02w03w110w011w115w216w317w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac3b2872…7d6a
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0x2bd1c200…56de
0x34b655…2a6f
4 touches
1 conflict
0x1cabcd31…ffdc
0x34b655…2a6f
4 touches
1 conflict
0x4f858307…7642
0x34b655…2a6f
4 touches
1 conflict
0x62030a81…91be
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x7aad02c6…b979
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 0xac3b287288…c67d6a
Audit this contract →
← previous block·next block →recent activity