← previous blocknext block →recent activity
Analyzing
Block #110,371,042
8 transactions · 7 stateful · 2026-10-04 04:28:24 UTC
Parallelism
63/100
Blocked
29%
Avg conflicts / tx
0.5
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #110,371,042 · 8 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
2w05w06w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xb4656137…5858
0x34b655…2a6f
4 touches
1 conflict
0x8c211514…b757
0x34b655…2a6f
4 touches
1 conflict
0x1408a100…f721
0x34b655…2a6f
2 touches
0 conflicts
0x32b33fca…1477
0x34b655…2a6f
2 touches
0 conflicts
0x47475f8a…2a88
0x34b655…2a6f
2 touches
0 conflicts
0x4ae1229c…569c
0x34b655…2a6f
2 touches
0 conflicts
0x4c215a60…73c1
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
3 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity