← previous blocknext block →recent activity
Analyzing
Block #106,371,267
27 transactions · 26 stateful · 2026-09-20 04:45:34 UTC
Parallelism
70/100
Blocked
46%
Avg conflicts / tx
1.22
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,371,267 · 27 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
1w02w13w24w35w46w57w68w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8d664414…3344
0x34b655…2a6f
16 touches
28 conflicts
0x9dd0a735…4d04
0x34b655…2a6f
10 touches
10 conflicts
0x809f2ba8…89d3
0x34b655…2a6f
10 touches
10 conflicts
0xb93f1ab3…c3d9
0x34b655…2a6f
8 touches
6 conflicts
0x1b25f260…c429
0x34b655…2a6f
8 touches
6 conflicts
0x2a6b4037…febd
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
8 touches
6 conflicts
0x6da5efbe…7e01
0x34b655…2a6f
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 0x8d664414de…103344
Audit this contract →
← previous block·next block →recent activity