← previous blocknext block →recent activity
Analyzing
Block #105,841,670
23 transactions · 22 stateful · 2026-09-18 08:19:00 UTC
Parallelism
57/100
Blocked
59%
Avg conflicts / tx
2.13
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #105,841,670 · 23 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
2w03w04w15w06w18w210w211w312w113w414w515w616w717w818w922w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5684aadd…8d62
0x34b655…2a6f
18 touches
36 conflicts
0xc824469a…6425
0x34b655…2a6f
16 touches
28 conflicts
0x7822b37f…9834
0x34b655…2a6f
14 touches
21 conflicts
0xc09c3422…3c8b
0x34b655…2a6f
10 touches
10 conflicts
0xc10b903d…2f54
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x2185f870…11f6
0x34b655…2a6f
6 touches
3 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 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
36 conflicts on slot 0x5684aadd69…f58d62
Audit this contract →
← previous block·next block →recent activity