← previous blocknext block →recent activity
Analyzing
Block #105,858,326
36 transactions · 34 stateful · 2026-09-18 09:42:58 UTC
Parallelism
58/100
Blocked
68%
Avg conflicts / tx
3.11
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #105,858,326 · 36 txs across 15 waves · depth 15
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w05w06w110w011w112w213w315w516w617w718w819w921w1122w1223w1324w1431w232w335w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
20 touches
45 conflicts
0x8db32935…81a7
0x34b655…2a6f
18 touches
36 conflicts
0xda5852d2…2e3f
0x34b655…2a6f
16 touches
28 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0x49890ced…6f23
0x34b655…2a6f
12 touches
15 conflicts
0x42522e76…2592
0x34b655…2a6f
12 touches
15 conflicts
0xcf6fb232…dbca
0x34b655…2a6f
12 touches
15 conflicts
0x1d9867ad…6d9a
0x34b655…2a6f
10 touches
10 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
45 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity