← previous blocknext block →recent activity
Analyzing
Block #100,141,064
20 transactions · 18 stateful · 2026-08-29 08:50:42 UTC
Parallelism
60/100
Blocked
56%
Avg conflicts / tx
1.8
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #100,141,064 · 20 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w07w18w210w211w313w314w416w517w618w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0xd66696e0…0842
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6426
0x34b655…2a6f
10 touches
10 conflicts
0xec2a8d79…70cb
0x34b655…2a6f
10 touches
10 conflicts
0xb38f11d9…038b
0x34b655…2a6f
10 touches
10 conflicts
0x50c61506…343f
0x34b655…2a6f
10 touches
10 conflicts
0x65389105…dfe9
0x34b655…2a6f
9 touches
10 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
21 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity