← previous blocknext block →recent activity
Analyzing
Block #105,846,218
27 transactions · 26 stateful · 2026-09-18 08:42:02 UTC
Parallelism
63/100
Blocked
58%
Avg conflicts / tx
1.7
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #105,846,218 · 27 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
1w02w17w08w110w011w113w214w115w216w317w418w519w620w721w822w925w126w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x469fa264…b1a8
0x34b655…2a6f
14 touches
21 conflicts
0x82f1ed07…ff68
0x34b655…2a6f
14 touches
21 conflicts
0x5a548af5…0eb0
0x34b655…2a6f
12 touches
15 conflicts
0x49890ced…6f23
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x0fd9f955…e86b
0x34b655…2a6f
8 touches
6 conflicts
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
0x60a536a6…ef7a
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
21 conflicts on slot 0x469fa264d1…53b1a8
Audit this contract →
← previous block·next block →recent activity