← previous blocknext block →recent activity
Analyzing
Block #110,135,470
24 transactions · 21 stateful · 2026-10-03 08:43:06 UTC
Parallelism
88/100
Blocked
10%
Avg conflicts / tx
0.08
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #110,135,470 · 24 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
1w07w123w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc53799eb…d928
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xf5dc501b…831c
0x34b655…2a6f
4 touches
1 conflict
0x19dcf812…44d9
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x7bd229ad…63b2
0x34b655…2a6f
4 touches
1 conflict
0x00000000…002d
0x1b6862…e19c
2 touches
0 conflicts
0x6235638c…643b
0x1b6862…e19c
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 0xc53799ebcf…a9d928
Audit this contract →
← previous block·next block →recent activity