← previous blocknext block →recent activity
Analyzing
Block #111,810,690
23 transactions · 18 stateful · 2026-10-09 05:18:06 UTC
Parallelism
87/100
Blocked
28%
Avg conflicts / tx
0.26
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #111,810,690 · 23 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
1w04w05w111w012w116w117w222w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x63ea5e6d…036c
0x34b655…2a6f
6 touches
3 conflicts
0x74e46435…fdcd
0x34b655…2a6f
4 touches
1 conflict
0x91cdfdeb…7feb
0x34b655…2a6f
4 touches
1 conflict
0xc1cb6f4e…bdb7
0x34b655…2a6f
4 touches
1 conflict
0xc1f12f12…c3ba
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xddd20e39…d524
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 0x63ea5e6d75…fb036c
Audit this contract →
← previous block·next block →recent activity