← previous blocknext block →recent activity
Analyzing
Block #106,190,775
26 transactions · 23 stateful · 2026-09-19 13:37:09 UTC
Parallelism
69/100
Blocked
65%
Avg conflicts / tx
1.58
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,190,775 · 26 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w16w07w111w213w214w215w317w418w519w620w725w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x58a5b9a1…5447
0x34b655…2a6f
14 touches
21 conflicts
0xd62f3741…b903
0x34b655…2a6f
14 touches
21 conflicts
0xe33beb97…6c6f
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xecd87a39…d9c5
0x34b655…2a6f
8 touches
6 conflicts
0xd17580f9…ece1
0x754704…b603
6 touches
3 conflicts
0x315e07b8…9823
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 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 0x58a5b9a123…885447
Audit this contract →
← previous block·next block →recent activity