← previous blocknext block →recent activity
Analyzing
Block #106,206,722
26 transactions · 25 stateful · 2026-09-19 14:57:27 UTC
Parallelism
69/100
Blocked
52%
Avg conflicts / tx
1.54
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,206,722 · 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
1w02w13w08w110w011w112w213w314w416w217w220w321w422w523w624w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xed0c288a…471c
0x34b655…2a6f
16 touches
28 conflicts
0xd17580f9…ece1
0x754704…b603
10 touches
10 conflicts
0x2d071de0…c86e
0x34b655…2a6f
8 touches
6 conflicts
0x98568c43…ff4e
0x34b655…2a6f
8 touches
6 conflicts
0xf6deafb5…5c25
0x34b655…2a6f
8 touches
6 conflicts
0xab981df1…2941
0x34b655…2a6f
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x24ed74ea…a3ff
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
28 conflicts on slot 0xed0c288aa1…6d471c
Audit this contract →
← previous block·next block →recent activity