← previous blocknext block →recent activity
Analyzing
Block #100,751,257
23 transactions · 21 stateful · 2026-08-31 12:04:33 UTC
Parallelism
70/100
Blocked
48%
Avg conflicts / tx
0.78
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #100,751,257 · 23 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
1w02w14w05w07w18w29w311w212w413w516w120w221w022w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x41c56387…a8f6
0x34b655…2a6f
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xec7d120d…7084
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0029
0x1b6862…e19c
4 touches
1 conflict
0x8d47c9a4…f11b
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x1d9154e7…8821
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
6 conflicts on slot 0x41c5638713…86a8f6
Audit this contract →
← previous block·next block →recent activity