← previous blocknext block →recent activity
Analyzing
Block #98,062,065
24 transactions · 17 stateful · 2026-08-22 01:30:30 UTC
Parallelism
88/100
Blocked
29%
Avg conflicts / tx
0.25
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #98,062,065 · 24 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w113w014w115w217w019w120w021w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3836a730…b3a9
0x34b655…2a6f
6 touches
3 conflicts
0x3f81bcfb…2905
0x40c49f…2af0
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x258fcaf5…2084
0x34b655…2a6f
4 touches
1 conflict
0x5d313602…a9aa
0x34b655…2a6f
4 touches
1 conflict
0x699ee60f…de01
0x34b655…2a6f
4 touches
1 conflict
0x7722b04e…2c21
0x34b655…2a6f
4 touches
1 conflict
0x7de57974…f5ba
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 0x3836a73066…21b3a9
Audit this contract →
← previous block·next block →recent activity