← previous blocknext block →recent activity
Analyzing
Block #106,951,838
13 transactions · 13 stateful · 2026-09-22 05:28:39 UTC
Parallelism
54/100
Blocked
38%
Avg conflicts / tx
1.15
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,951,838 · 13 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w27w38w49w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd77c6481…af41
0x34b655…2a6f
12 touches
15 conflicts
0x67287ef9…2d07
0x34b655…2a6f
10 touches
10 conflicts
0xef5959a3…2a2f
0x34b655…2a6f
8 touches
6 conflicts
0xab41643c…f9bf
0x34b655…2a6f
6 touches
3 conflicts
0x42102e63…8aa9
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
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
15 conflicts on slot 0xd77c648179…71af41
Audit this contract →
← previous block·next block →recent activity