← previous blocknext block →recent activity
Analyzing
Block #105,841,690
22 transactions · 21 stateful · 2026-09-18 08:19:06 UTC
Parallelism
55/100
Blocked
57%
Avg conflicts / tx
2
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #105,841,690 · 22 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
2w04w15w210w211w312w413w514w615w716w817w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
18 touches
36 conflicts
0x5684aadd…8d62
0x34b655…2a6f
18 touches
36 conflicts
0x3492a206…c5c6
0x34b655…2a6f
10 touches
10 conflicts
0x7dba3206…9c03
0x34b655…2a6f
10 touches
10 conflicts
0x8ae87135…d426
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0xfddb21bb…380d
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
36 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity