← previous blocknext block →recent activity
Analyzing
Block #100,155,964
26 transactions · 20 stateful · 2026-08-29 10:05:42 UTC
Parallelism
65/100
Blocked
55%
Avg conflicts / tx
1.62
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #100,155,964 · 26 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w07w19w214w315w417w518w619w721w422w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x50c61506…343f
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x5b305b76…44c5
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0x5e1822f4…c400
0x34b655…2a6f
8 touches
6 conflicts
0x35b89cd8…5092
0x34b655…2a6f
6 touches
3 conflicts
0x261cbea7…e35d
0x34b655…2a6f
6 touches
3 conflicts
0x97420b44…a2a8
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
21 conflicts on slot 0x50c615063f…63343f
Audit this contract →
← previous block·next block →recent activity