← previous blocknext block →recent activity
Analyzing
Block #106,415,156
20 transactions · 19 stateful · 2026-09-20 08:26:27 UTC
Parallelism
65/100
Blocked
42%
Avg conflicts / tx
0.95
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,415,156 · 20 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
1w02w13w24w35w46w010w112w213w519w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd563f3a1…94b1
0x34b655…2a6f
12 touches
15 conflicts
0x4cf825c3…0e8d
0x34b655…2a6f
10 touches
10 conflicts
0x000bde1a…e123
0x34b655…2a6f
8 touches
6 conflicts
0xb9b077a8…e029
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xb71811c4…ca25
0x34b655…2a6f
6 touches
3 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
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 0xd563f3a18c…f494b1
Audit this contract →
← previous block·next block →recent activity