← previous blocknext block →recent activity
Analyzing
Block #106,164,314
21 transactions · 21 stateful · 2026-09-19 11:23:59 UTC
Parallelism
62/100
Blocked
76%
Avg conflicts / tx
2.29
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,164,314 · 21 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
1w02w13w24w35w06w07w18w29w110w211w312w413w514w415w516w617w719w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x33fa06a2…87b1
0x34b655…2a6f
16 touches
28 conflicts
0x19cb4cde…bfd9
0x34b655…2a6f
14 touches
21 conflicts
0x92b49f44…ee4f
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…001e
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002e
0x1b6862…e19c
8 touches
6 conflicts
0x6aa624fd…a851
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 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
28 conflicts on slot 0x33fa06a25e…3b87b1
Audit this contract →
← previous block·next block →recent activity