← previous blocknext block →recent activity
Analyzing
Block #111,847,709
16 transactions · 14 stateful · 2026-10-09 08:24:21 UTC
Parallelism
81/100
Blocked
29%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #111,847,709 · 16 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w06w17w211w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbde524f4…43bf
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xb686e6f5…f6d1
0xc8689a…ee79
4 touches
1 conflict
0x0dbcadee…ff1c
0x34b655…2a6f
2 touches
0 conflicts
0x197824df…58fe
0x34b655…2a6f
2 touches
0 conflicts
0x1c385c8c…a0fb
0x34b655…2a6f
2 touches
0 conflicts
0x21b9e637…f417
0x34b655…2a6f
2 touches
0 conflicts
0x27c14b20…4276
0x34b655…2a6f
2 touches
0 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
3 conflicts on slot 0xbde524f475…b143bf
Audit this contract →
← previous block·next block →recent activity