← previous blocknext block →recent activity
Analyzing
Block #110,392,177
17 transactions · 17 stateful · 2026-10-04 06:14:44 UTC
Parallelism
82/100
Blocked
29%
Avg conflicts / tx
0.41
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #110,392,177 · 17 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
5w06w110w012w013w114w215w216w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x81622051…deeb
0x34b655…2a6f
6 touches
3 conflicts
0xccfc532d…7770
0x34b655…2a6f
4 touches
1 conflict
0xe720a4c6…8eb0
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0x0d69b170…f45b
0x34b655…2a6f
4 touches
1 conflict
0x4073f47e…39e6
0x34b655…2a6f
4 touches
1 conflict
0x4cc61cd1…d304
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 0x816220515a…18deeb
Audit this contract →
← previous block·next block →recent activity