← previous blocknext block →recent activity
Analyzing
Block #105,870,060
33 transactions · 33 stateful · 2026-09-18 10:42:01 UTC
Parallelism
48/100
Blocked
70%
Avg conflicts / tx
3.67
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #105,870,060 · 33 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
1w02w13w24w35w26w07w213w314w117w418w519w620w721w822w923w1024w1125w1226w1327w1432w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9dccd2a9…2790
0x34b655…2a6f
30 touches
105 conflicts
0xc824469a…6425
0x34b655…2a6f
28 touches
91 conflicts
0x17094aa6…87fc
0x34b655…2a6f
14 touches
21 conflicts
0x49890ced…6f23
0x34b655…2a6f
12 touches
15 conflicts
0xd79c9727…1233
0x34b655…2a6f
12 touches
15 conflicts
0xdef81c0c…4eb5
0x34b655…2a6f
12 touches
15 conflicts
0x42522e76…2592
0x34b655…2a6f
12 touches
15 conflicts
0x89999c15…fdac
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
105 conflicts on slot 0x9dccd2a98b…6d2790
Audit this contract →
← previous block·next block →recent activity