← previous blocknext block →recent activity
Analyzing
Block #106,934,076
19 transactions · 19 stateful · 2026-09-22 03:59:15 UTC
Parallelism
68/100
Blocked
37%
Avg conflicts / tx
0.95
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,934,076 · 19 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
1w02w13w26w07w18w29w310w411w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe720a4c6…8eb0
0x34b655…2a6f
12 touches
15 conflicts
0xd1b40f29…9b9d
0x34b655…2a6f
12 touches
15 conflicts
0xb7aa9720…56df
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…002d
0x1b6862…e19c
6 touches
3 conflicts
0xd18a8dca…452e
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001d
0x1b6862…e19c
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
15 conflicts on slot 0xe720a4c698…508eb0
Audit this contract →
← previous block·next block →recent activity