← previous blocknext block →recent activity
Analyzing
Block #106,457,300
24 transactions · 23 stateful · 2026-09-20 11:58:37 UTC
Parallelism
58/100
Blocked
57%
Avg conflicts / tx
2.29
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #106,457,300 · 24 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w08w19w210w113w314w415w516w617w718w819w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5472a243…f70d
0x34b655…2a6f
20 touches
45 conflicts
0xdf64e5e6…75e8
0x34b655…2a6f
14 touches
21 conflicts
0x89eaf36a…4e48
0x34b655…2a6f
12 touches
15 conflicts
0x310a7246…2dcb
0x34b655…2a6f
12 touches
15 conflicts
0x809f2ba8…89d3
0x34b655…2a6f
10 touches
10 conflicts
0x1b25f260…c429
0x34b655…2a6f
8 touches
6 conflicts
0xeee76313…70b5
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
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
45 conflicts on slot 0x5472a24372…42f70d
Audit this contract →
← previous block·next block →recent activity