← previous blocknext block →recent activity
Analyzing
Block #106,931,184
19 transactions · 18 stateful · 2026-09-22 03:44:42 UTC
Parallelism
63/100
Blocked
67%
Avg conflicts / tx
1.21
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,931,184 · 19 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w06w17w28w39w410w511w012w113w214w316w417w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xba1edffb…323e
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xccebf5c5…8758
0x34b655…2a6f
8 touches
6 conflicts
0xd125c3f8…99aa
0x34b655…2a6f
8 touches
6 conflicts
0xd1524132…52f1
0x34b655…2a6f
8 touches
6 conflicts
0x3273cbc8…b4c8
0x34b655…2a6f
8 touches
6 conflicts
0xfaf89f45…ced6
0x34b655…2a6f
8 touches
6 conflicts
0x3780a34a…b50a
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
6 conflicts on slot 0xba1edffb42…64323e
Audit this contract →
← previous block·next block →recent activity