← previous blocknext block →recent activity
Analyzing
Block #105,930,032
30 transactions · 27 stateful · 2026-09-18 15:44:45 UTC
Parallelism
87/100
Blocked
33%
Avg conflicts / tx
0.53
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #105,930,032 · 30 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w16w07w18w09w211w013w114w223w124w326w027w128w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xefb236ca…f49b
0x34b655…2a6f
8 touches
6 conflicts
0x8b01b875…e8bd
0x34b655…2a6f
6 touches
3 conflicts
0x808d3d3a…f8d7
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x4681609f…6493
0x34b655…2a6f
4 touches
1 conflict
0x49890ced…6f23
0x34b655…2a6f
4 touches
1 conflict
0x581b829b…9578
0x34b655…2a6f
4 touches
1 conflict
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
6 conflicts on slot 0xefb236ca8b…0ff49b
Audit this contract →
← previous block·next block →recent activity