← previous blocknext block →recent activity
Analyzing
Block #101,854,414
33 transactions · 18 stateful · 2026-09-04 08:35:02 UTC
Parallelism
67/100
Blocked
61%
Avg conflicts / tx
1.39
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #101,854,414 · 33 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w06w18w221w322w426w427w531w932w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
16 touches
28 conflicts
0x482471ad…122f
0x34b655…2a6f
14 touches
21 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0xec7d120d…7084
0x34b655…2a6f
8 touches
6 conflicts
0xb409e204…89ac
0x34b655…2a6f
8 touches
6 conflicts
0x735a86cd…b64d
0x34b655…2a6f
6 touches
3 conflicts
0xdbf974a4…b232
0x34b655…2a6f
6 touches
3 conflicts
0x4bee6a8d…465e
0x34b655…2a6f
5 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
28 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity