← previous blocknext block →recent activity
Analyzing
Block #106,403,372
24 transactions · 20 stateful · 2026-09-20 07:27:08 UTC
Parallelism
83/100
Blocked
35%
Avg conflicts / tx
0.46
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,403,372 · 24 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w36w09w010w111w221w123w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc71de274…0c33
0x34b655…2a6f
8 touches
6 conflicts
0xd563f3a1…94b1
0x34b655…2a6f
8 touches
6 conflicts
0x54f7f60f…43cc
0x34b655…2a6f
6 touches
3 conflicts
0x53ca1284…cb2c
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x8b52b75c…8a0d
0xa6afd3…d132
4 touches
1 conflict
0x1b25f260…c429
0x34b655…2a6f
4 touches
1 conflict
0x49b9fdd5…9c16
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
6 conflicts on slot 0xc71de274e6…b50c33
Audit this contract →
← previous block·next block →recent activity