← previous blocknext block →recent activity
Analyzing
Block #111,847,724
20 transactions · 20 stateful · 2026-10-09 08:24:26 UTC
Parallelism
75/100
Blocked
25%
Avg conflicts / tx
0.45
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #111,847,724 · 20 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w07w08w113w115w216w317w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcfabbd39…24f3
0x34b655…2a6f
8 touches
6 conflicts
0x1d0c271c…eef8
0x34b655…2a6f
6 touches
3 conflicts
0x9a8482cc…8bee
0x34b655…2a6f
6 touches
3 conflicts
0xcc198496…cf94
0x34b655…2a6f
6 touches
3 conflicts
0x1867b653…e61b
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
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 0xcfabbd397a…d324f3
Audit this contract →
← previous block·next block →recent activity