← previous blocknext block →recent activity
Analyzing
Block #111,072,335
22 transactions · 18 stateful · 2026-10-06 15:21:22 UTC
Parallelism
91/100
Blocked
28%
Avg conflicts / tx
0.23
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #111,072,335 · 22 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w04w18w012w113w014w115w116w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x81baaa00…7e68
0x34b655…2a6f
4 touches
1 conflict
0x85527a3c…c476
0x34b655…2a6f
4 touches
1 conflict
0x8590b692…b267
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xcb3899c4…169e
0x34b655…2a6f
4 touches
1 conflict
0xccebf5c5…8758
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
1 conflict on slot 0x81baaa00b3…eb7e68
Audit this contract →
← previous block·next block →recent activity