← previous blocknext block →recent activity
Analyzing
Block #105,841,858
16 transactions · 16 stateful · 2026-09-18 08:19:58 UTC
Parallelism
63/100
Blocked
44%
Avg conflicts / tx
1.25
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #105,841,858 · 16 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w06w08w19w210w311w412w514w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5684aadd…8d62
0x34b655…2a6f
12 touches
15 conflicts
0x7c08286a…ecaa
0x34b655…2a6f
10 touches
10 conflicts
0xec2a8d79…70cb
0x34b655…2a6f
8 touches
6 conflicts
0xc10b903d…2f54
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x689bcce4…554a
0x34b655…2a6f
4 touches
1 conflict
0x42522e76…2592
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
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
15 conflicts on slot 0x5684aadd69…f58d62
Audit this contract →
← previous block·next block →recent activity