← previous blocknext block →recent activity
Analyzing
Block #105,842,213
38 transactions · 35 stateful · 2026-09-18 08:21:45 UTC
Parallelism
58/100
Blocked
51%
Avg conflicts / tx
2.79
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #105,842,213 · 38 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
1w02w03w15w08w011w016w219w120w221w322w423w524w625w726w827w928w1029w1130w1234w435w1336w14
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
26 touches
78 conflicts
0x5a548af5…0eb0
0x34b655…2a6f
20 touches
45 conflicts
0xa6d40b7f…2969
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x814ba1ee…5451
0x34b655…2a6f
8 touches
6 conflicts
0x3ead1ba2…29f5
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
78 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity