← previous blocknext block →recent activity
Analyzing
Block #99,502,661
11 transactions · 10 stateful · 2026-08-27 03:03:08 UTC
Parallelism
82/100
Blocked
10%
Avg conflicts / tx
0.09
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,502,661 · 11 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
6w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x261cbea7…e35e
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35d
0x34b655…2a6f
4 touches
1 conflict
0xf29ce086…fc39
0x34b655…2a6f
3 touches
1 conflict
0x4716aeb8…8f7b
0x34b655…2a6f
3 touches
1 conflict
0x0c7deec4…77cb
0x34b655…2a6f
2 touches
0 conflicts
0x992e9613…daaa
0x34b655…2a6f
2 touches
0 conflicts
0xac808a27…82db
0x34b655…2a6f
2 touches
0 conflicts
0xbd22d0fc…64fd
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