← previous blocknext block →recent activity
Analyzing
Block #106,435,177
30 transactions · 24 stateful · 2026-09-20 10:07:13 UTC
Parallelism
70/100
Blocked
67%
Avg conflicts / tx
1.4
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #106,435,177 · 30 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w16w27w08w09w114w316w417w518w620w622w724w826w129w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2a6b4037…febd
0x34b655…2a6f
14 touches
21 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001b
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002b
0x1b6862…e19c
6 touches
3 conflicts
0x3a3097d7…2ab5
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x000bde1a…e123
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
21 conflicts on slot 0x2a6b40371b…66febd
Audit this contract →
← previous block·next block →recent activity