← previous blocknext block →recent activity
Analyzing
Block #105,643,188
52 transactions · 47 stateful · 2026-09-17 15:38:45 UTC
Parallelism
69/100
Blocked
70%
Avg conflicts / tx
3.06
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #105,643,188 · 52 txs across 16 waves · depth 16
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w06w07w18w29w210w315w320w121w222w323w424w530w332w233w535w336w437w538w639w740w841w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x86bd79a5…1f48
0x34b655…2a6f
28 touches
91 conflicts
0x49890ced…6f23
0x34b655…2a6f
14 touches
21 conflicts
0x6771eae2…7014
0x34b655…2a6f
14 touches
21 conflicts
0x706c758c…2fdb
0x34b655…2a6f
14 touches
21 conflicts
0x3a68d7c1…372f
0x34b655…2a6f
12 touches
15 conflicts
0x42522e76…2592
0x34b655…2a6f
12 touches
15 conflicts
0x88e92ec7…696d
0x34b655…2a6f
12 touches
15 conflicts
0x7fb43647…e0bd
0x34b655…2a6f
12 touches
15 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
91 conflicts on slot 0x86bd79a5a6…961f48
Audit this contract →
← previous block·next block →recent activity