← previous blocknext block →recent activity
Analyzing
Block #105,848,461
51 transactions · 42 stateful · 2026-09-18 08:53:19 UTC
Parallelism
82/100
Blocked
62%
Avg conflicts / tx
1.61
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #105,848,461 · 51 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w07w08w110w211w113w214w316w223w231w734w236w340w341w442w543w644w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4681609f…6493
0x34b655…2a6f
14 touches
21 conflicts
0xbb30d34f…b21b
0x34b655…2a6f
14 touches
21 conflicts
0xdfce7dfe…5053
0x34b655…2a6f
12 touches
15 conflicts
0x72b31f58…619a
0x34b655…2a6f
10 touches
10 conflicts
0xbde524f4…43bf
0x34b655…2a6f
10 touches
10 conflicts
0xeb3646f9…0007
0x34b655…2a6f
10 touches
10 conflicts
0xd1480c90…ae0b
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
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
21 conflicts on slot 0x4681609fd4…e96493
Audit this contract →
← previous block·next block →recent activity