← previous blocknext block →recent activity
Analyzing
Block #111,931,166
26 transactions · 23 stateful · 2026-10-09 15:24:16 UTC
Parallelism
81/100
Blocked
39%
Avg conflicts / tx
0.54
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #111,931,166 · 26 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
1w02w15w06w07w19w010w111w215w121w222w323w424w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2afdfdbf…4a62
0x34b655…2a6f
6 touches
3 conflicts
0xb6c4f8c7…273f
0x34b655…2a6f
6 touches
3 conflicts
0xb6fcbbb7…2b31
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x827786de…38cb
0x34b655…2a6f
6 touches
3 conflicts
0x784d7a94…949c
0x1b6862…e19c
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x00387cd2…9e57
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
3 conflicts on slot 0x2afdfdbfb5…8a4a62
Audit this contract →
← previous block·next block →recent activity