← previous blocknext block →recent activity
Analyzing
Block #106,554,243
23 transactions · 23 stateful · 2026-09-20 20:06:30 UTC
Parallelism
65/100
Blocked
48%
Avg conflicts / tx
1.48
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,554,243 · 23 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
1w02w13w14w25w08w19w212w013w114w315w416w517w619w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x72d35c7e…525e
0x34b655…2a6f
14 touches
21 conflicts
0xe098738f…9bbe
0x34b655…2a6f
10 touches
10 conflicts
0xfe65bb7b…12d7
0x34b655…2a6f
8 touches
6 conflicts
0x1b25f260…c429
0x34b655…2a6f
8 touches
6 conflicts
0x4986f2ad…8151
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
8 touches
6 conflicts
0x773f594b…a1ea
0x34b655…2a6f
8 touches
6 conflicts
0x86cea35b…bdff
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
21 conflicts on slot 0x72d35c7e72…07525e
Audit this contract →
← previous block·next block →recent activity