← previous blocknext block →recent activity
Analyzing
Block #105,606,510
29 transactions · 29 stateful · 2026-09-17 12:34:06 UTC
Parallelism
66/100
Blocked
59%
Avg conflicts / tx
1.9
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #105,606,510 · 29 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
2w03w14w08w19w210w311w412w514w215w318w419w620w721w822w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb7b16dd0…0426
0x34b655…2a6f
16 touches
28 conflicts
0xed3b0943…f01b
0x34b655…2a6f
12 touches
15 conflicts
0x42522e76…2592
0x34b655…2a6f
10 touches
10 conflicts
0x49890ced…6f23
0x34b655…2a6f
10 touches
10 conflicts
0x4e135144…4167
0x34b655…2a6f
10 touches
10 conflicts
0x38bcfe5f…6c71
0x34b655…2a6f
10 touches
10 conflicts
0xa1392ea8…8747
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
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 0xb7b16dd022…c80426
Audit this contract →
← previous block·next block →recent activity