← previous blocknext block →recent activity
Analyzing
Block #99,260,703
12 transactions · 10 stateful · 2026-08-26 06:45:03 UTC
Parallelism
83/100
Blocked
10%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,260,703 · 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
7w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcd26fba5…21c6
0x34b655…2a6f
4 touches
1 conflict
0xbaf6ed88…c179
0x34b655…2a6f
4 touches
1 conflict
0xc3baa205…f26e
0x34b655…2a6f
4 touches
1 conflict
0x703727d4…b1c0
0x34b655…2a6f
4 touches
1 conflict
0x1951ee47…540f
0x34b655…2a6f
2 touches
0 conflicts
0x1be8e7b8…0eb1
0x34b655…2a6f
2 touches
0 conflicts
0x34e43087…a2c4
0x34b655…2a6f
2 touches
0 conflicts
0x38a429dd…bcb0
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 0xcd26fba530…bd21c6
Audit this contract →
← previous block·next block →recent activity