← previous blocknext block →recent activity
Analyzing
Block #106,235,182
33 transactions · 29 stateful · 2026-09-19 17:20:45 UTC
Parallelism
76/100
Blocked
69%
Avg conflicts / tx
1.36
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,235,182 · 33 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w09w010w111w113w316w117w419w620w621w723w232w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1a84e266…4f8a
0x34b655…2a6f
10 touches
10 conflicts
0x0e80a367…d8ce
0xd32edf…ff58
9 touches
10 conflicts
0x67e04055…2610
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
8 touches
6 conflicts
0xd17580f9…ece1
0x754704…b603
8 touches
6 conflicts
0x00000000…002f
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0xa3ed5a09…c6d3
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
10 conflicts on slot 0x1a84e266a3…f64f8a
Audit this contract →
← previous block·next block →recent activity