← previous blocknext block →recent activity
Analyzing
Block #106,215,632
36 transactions · 29 stateful · 2026-09-19 15:42:18 UTC
Parallelism
83/100
Blocked
59%
Avg conflicts / tx
0.89
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,215,632 · 36 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
1w02w13w24w35w06w28w411w113w219w021w125w226w327w228w329w435w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x638cd0f2…cb93
0x34b655…2a6f
10 touches
10 conflicts
0x4863dc19…619d
0x34b655…2a6f
8 touches
6 conflicts
0xd17580f9…ece1
0x754704…b603
8 touches
6 conflicts
0xea1eaa00…2116
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…002f
0x1b6862…e19c
6 touches
3 conflicts
0xd8d828a7…b64f
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
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 0x638cd0f243…88cb93
Audit this contract →
← previous block·next block →recent activity