← previous blocknext block →recent activity
Analyzing
Block #105,843,683
35 transactions · 31 stateful · 2026-09-18 08:29:15 UTC
Parallelism
51/100
Blocked
65%
Avg conflicts / tx
3.29
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #105,843,683 · 35 txs across 17 waves · depth 17
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
wave w16
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w36w07w013w118w219w320w421w522w623w724w825w926w1028w1232w1433w1534w16
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
28 touches
91 conflicts
0xd2a24d67…eb6d
0x34b655…2a6f
14 touches
21 conflicts
0x5a548af5…0eb0
0x34b655…2a6f
14 touches
21 conflicts
0x3ead1ba2…29f5
0x34b655…2a6f
12 touches
15 conflicts
0xa6d40b7f…2969
0x34b655…2a6f
12 touches
15 conflicts
0x42522e76…2592
0x34b655…2a6f
10 touches
10 conflicts
0x49890ced…6f23
0x34b655…2a6f
10 touches
10 conflicts
0x1cbbde54…8ff9
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
91 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity