← previous blocknext block →recent activity
Analyzing
Block #98,536,926
12 transactions · 12 stateful · 2026-08-23 17:27:44 UTC
Parallelism
83/100
Blocked
8%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #98,536,926 · 12 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x261cbea7…e35e
0x34b655…2a6f
4 touches
1 conflict
0x7167f871…ddb3
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35d
0x34b655…2a6f
4 touches
1 conflict
0x27b6010e…e4aa
0x34b655…2a6f
2 touches
0 conflicts
0x422eb577…203f
0x34b655…2a6f
2 touches
0 conflicts
0x68ec1d3b…cba0
0x34b655…2a6f
2 touches
0 conflicts
0x699ee60f…de01
0x34b655…2a6f
2 touches
0 conflicts
0x7bf9b8e3…fcba
0x34b655…2a6f
2 touches
0 conflicts
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
1 conflict on slot 0x261cbea79d…12e35e
Audit this contract →
← previous block·next block →recent activity