← previous blocknext block →recent activity
Analyzing
Block #98,458,786
7 transactions · 7 stateful · 2026-08-23 10:47:24 UTC
Parallelism
71/100
Blocked
14%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #98,458,786 · 7 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
1w04w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd3f6a188…324f
0x34b655…2a6f
4 touches
1 conflict
0x544745e8…d72e
0x34b655…2a6f
4 touches
1 conflict
0x0505bae8…b4fb
0x34b655…2a6f
2 touches
0 conflicts
0x094c7530…e7b4
0x34b655…2a6f
2 touches
0 conflicts
0x12e7c471…901c
0x34b655…2a6f
2 touches
0 conflicts
0x1f5e81d7…e21e
0x34b655…2a6f
2 touches
0 conflicts
0x2c97e962…ce1d
0x34b655…2a6f
2 touches
0 conflicts
0x58b8efd6…2945
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 0xd3f6a18828…cf324f
Audit this contract →
← previous block·next block →recent activity