← previous blocknext block →recent activity
Analyzing
Block #110,380,961
24 transactions · 21 stateful · 2026-10-04 05:18:17 UTC
Parallelism
58/100
Blocked
57%
Avg conflicts / tx
1.96
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #110,380,961 · 24 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w416w217w318w419w520w621w722w823w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0xbd590df7…9891
0x34b655…2a6f
16 touches
28 conflicts
0xe1c4e5ce…0dec
0x34b655…2a6f
16 touches
28 conflicts
0xb0f5d668…99ac
0x34b655…2a6f
14 touches
21 conflicts
0x9abad0e8…28a3
0x34b655…2a6f
12 touches
15 conflicts
0xfcb96258…a362
0xd32edf…ff58
9 touches
10 conflicts
0x2351000d…1753
0x34b655…2a6f
8 touches
6 conflicts
0xfae7100c…9c20
0x34b655…2a6f
8 touches
6 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
28 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity