← previous blocknext block →recent activity
Analyzing
Block #106,931,221
26 transactions · 24 stateful · 2026-09-22 03:44:53 UTC
Parallelism
62/100
Blocked
54%
Avg conflicts / tx
1.35
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #106,931,221 · 26 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w17w08w19w210w311w412w513w614w715w816w920w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x810a3aa2…0227
0x34b655…2a6f
14 touches
21 conflicts
0xb6a59002…65eb
0x34b655…2a6f
12 touches
15 conflicts
0x42522e76…2592
0x34b655…2a6f
12 touches
15 conflicts
0xba1edffb…323e
0x34b655…2a6f
10 touches
10 conflicts
0xe720a4c6…8eb0
0x34b655…2a6f
8 touches
6 conflicts
0x3780a34a…b50a
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
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
21 conflicts on slot 0x810a3aa264…c40227
Audit this contract →
← previous block·next block →recent activity