← previous blocknext block →recent activity
Analyzing
Block #111,839,610
9 transactions · 9 stateful · 2026-10-09 07:43:36 UTC
Parallelism
78/100
Blocked
11%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #111,839,610 · 9 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
5w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x669c07b3…c161
0x34b655…2a6f
4 touches
1 conflict
0x1de99a3f…fb6f
0x34b655…2a6f
4 touches
1 conflict
0xe90f6b39…7749
0x34b655…2a6f
4 touches
1 conflict
0x4f363b3a…4b87
0x34b655…2a6f
4 touches
1 conflict
0x8919c78e…7e9e
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0x1fb37a…a010
2 touches
0 conflicts
0x14fe1598…d0ba
0x34b655…2a6f
2 touches
0 conflicts
0x47ee9f76…8dee
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
1 conflict on slot 0x669c07b348…67c161
Audit this contract →
← previous block·next block →recent activity