← previous blocknext block →recent activity
Analyzing
Block #100,080,709
21 transactions · 18 stateful · 2026-08-29 03:46:40 UTC
Parallelism
67/100
Blocked
50%
Avg conflicts / tx
1.1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #100,080,709 · 21 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w16w08w09w110w111w212w314w417w518w619w020w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x50c61506…343f
0x34b655…2a6f
12 touches
15 conflicts
0x33206d3d…8b20
0x34b655…2a6f
8 touches
6 conflicts
0x69ee34d1…30f8
0x34b655…2a6f
6 touches
3 conflicts
0xd895ee0b…d301
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x7dbb5075…c917
0x34b655…2a6f
6 touches
3 conflicts
0xec2a8d79…70cb
0x34b655…2a6f
6 touches
3 conflicts
0xe720a4c6…8eb0
0x34b655…2a6f
6 touches
3 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
15 conflicts on slot 0x50c615063f…63343f
Audit this contract →
← previous block·next block →recent activity