← previous blocknext block →recent activity
Analyzing
Block #110,321,876
119 transactions · 118 stateful · 2026-10-04 00:21:02 UTC
Parallelism
95/100
Blocked
7%
Avg conflicts / tx
0.2
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #110,321,876 · 119 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w08w09w1110w1112w0114w1115w2116w3117w4118w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0xbd590df7…9891
0x34b655…2a6f
10 touches
10 conflicts
0xe1c4e5ce…0dec
0x34b655…2a6f
10 touches
10 conflicts
0xfae7100c…9c20
0x34b655…2a6f
8 touches
6 conflicts
0xb0f5d668…99ac
0x34b655…2a6f
6 touches
3 conflicts
0x7fcecf25…332a
0x34b655…2a6f
6 touches
3 conflicts
0x4e45bb49…2491
0x34b655…2a6f
4 touches
1 conflict
0x8c211514…b757
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
15 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity