← previous blocknext block →recent activity
Analyzing
Block #100,111,191
18 transactions · 18 stateful · 2026-08-29 06:20:08 UTC
Parallelism
78/100
Blocked
28%
Avg conflicts / tx
0.67
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,111,191 · 18 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
3w04w05w18w110w011w212w317w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0476d77b…a514
0x34b655…2a6f
6 touches
3 conflicts
0x8c52ced7…6625
0x34b655…2a6f
6 touches
3 conflicts
0x1e168c8b…6945
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x6b267bdf…b173
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 0x0476d77bba…41a514
Audit this contract →
← previous block·next block →recent activity