← previous blocknext block →recent activity
Analyzing
Block #106,206,875
21 transactions · 19 stateful · 2026-09-19 14:58:13 UTC
Parallelism
81/100
Blocked
37%
Avg conflicts / tx
0.48
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,206,875 · 21 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
7w08w112w113w215w216w318w220w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x20500652…f7a1
0x34b655…2a6f
6 touches
3 conflicts
0xecc47c05…c3f6
0x34b655…2a6f
6 touches
3 conflicts
0x98568c43…ff4e
0x34b655…2a6f
6 touches
3 conflicts
0x24ed74ea…a3ff
0x34b655…2a6f
6 touches
3 conflicts
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x839c0c71…bada
0x34b655…2a6f
4 touches
1 conflict
0xb75367ff…a2b7
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
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
3 conflicts on slot 0x20500652cc…60f7a1
Audit this contract →
← previous block·next block →recent activity