← previous blocknext block →recent activity
Analyzing
Block #105,841,154
31 transactions · 30 stateful · 2026-09-18 08:16:24 UTC
Parallelism
74/100
Blocked
57%
Avg conflicts / tx
1.42
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #105,841,154 · 31 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w26w37w48w59w610w722w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb2c6c770…dc41
0x34b655…2a6f
16 touches
28 conflicts
0xb482658a…e4f5
0x34b655…2a6f
16 touches
28 conflicts
0x90a021f0…f922
0x34b655…2a6f
10 touches
10 conflicts
0xb15c58ec…bd83
0x34b655…2a6f
10 touches
10 conflicts
0x923886df…0f39
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x42522e76…2592
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 0xb2c6c77013…98dc41
Audit this contract →
← previous block·next block →recent activity