← previous blocknext block →recent activity
Analyzing
Block #105,376,450
28 transactions · 27 stateful · 2026-09-16 17:16:09 UTC
Parallelism
75/100
Blocked
48%
Avg conflicts / tx
1.14
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #105,376,450 · 28 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w17w08w110w211w312w413w014w115w216w319w520w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0xc40c1915…55ed
0x34b655…2a6f
8 touches
6 conflicts
0x1375ab34…9901
0x6f6493…b480
7 touches
6 conflicts
0x1375ab34…9905
0x6f6493…b480
7 touches
6 conflicts
0x158839ee…500f
0x6f6493…b480
7 touches
6 conflicts
0x165be402…adfe
0x6f6493…b480
7 touches
6 conflicts
0x1958fcc6…b639
0x6f6493…b480
7 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
21 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity