← previous blocknext block →recent activity
Analyzing
Block #105,843,438
38 transactions · 38 stateful · 2026-09-18 08:28:00 UTC
Parallelism
66/100
Blocked
63%
Avg conflicts / tx
2.26
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #105,843,438 · 38 txs across 13 waves · depth 13
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w06w07w19w210w311w012w113w220w322w123w425w226w427w528w629w730w831w932w1033w1134w1235w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb0b0260c…51c4
0x34b655…2a6f
16 touches
28 conflicts
0x819f1c16…e41c
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0xfd7f5b55…4994
0x34b655…2a6f
12 touches
15 conflicts
0x9210e826…1414
0x34b655…2a6f
10 touches
10 conflicts
0x3e3f27ce…580c
0x34b655…2a6f
10 touches
10 conflicts
0x42522e76…2592
0x34b655…2a6f
10 touches
10 conflicts
0x49890ced…6f23
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
28 conflicts on slot 0xb0b0260c5f…e551c4
Audit this contract →
← previous block·next block →recent activity