← previous blocknext block →recent activity
Analyzing
Block #111,810,725
23 transactions · 21 stateful · 2026-10-09 05:18:16 UTC
Parallelism
78/100
Blocked
48%
Avg conflicts / tx
0.61
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #111,810,725 · 23 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
1w03w04w16w17w08w010w011w113w114w215w316w420w221w322w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0505bae8…b4fb
0x34b655…2a6f
6 touches
3 conflicts
0x3bdd71a2…b6eb
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xca2a134b…1c5b
0x34b655…2a6f
6 touches
3 conflicts
0x261cbea7…e35e
0x34b655…2a6f
4 touches
1 conflict
0x2f8f0724…0b92
0x34b655…2a6f
4 touches
1 conflict
0x58733c38…f2cd
0xe52b14…7230
4 touches
1 conflict
0x7d9ef283…ddd1
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 0x0505bae898…14b4fb
Audit this contract →
← previous block·next block →recent activity