← previous blocknext block →recent activity
Analyzing
Block #99,586,920
24 transactions · 23 stateful · 2026-08-27 10:10:07 UTC
Parallelism
83/100
Blocked
22%
Avg conflicts / tx
0.33
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,586,920 · 24 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w06w08w110w011w112w215w019w223w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xff6a8534…011c
0x34b655…2a6f
6 touches
3 conflicts
0x51fc8795…1266
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x53103bb4…02a1
0x34b655…2a6f
4 touches
1 conflict
0x8a02d049…f481
0x34b655…2a6f
4 touches
1 conflict
0x948836ff…59ab
0x34b655…2a6f
4 touches
1 conflict
0x9fc6ea79…e2dc
0x34b655…2a6f
4 touches
1 conflict
0xc1a4c088…e828
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 0xff6a853475…25011c
Audit this contract →
← previous block·next block →recent activity