← previous blocknext block →recent activity
Analyzing
Block #106,931,041
23 transactions · 22 stateful · 2026-09-22 03:43:59 UTC
Parallelism
52/100
Blocked
73%
Avg conflicts / tx
2.83
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #106,931,041 · 23 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w15w38w29w311w412w513w114w416w617w718w819w920w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5f41438c…0d4f
0x34b655…2a6f
22 touches
55 conflicts
0x704a8131…bbe8
0x34b655…2a6f
12 touches
15 conflicts
0xc8c615d4…5da3
0x34b655…2a6f
10 touches
10 conflicts
0x810a3aa2…0227
0x34b655…2a6f
10 touches
10 conflicts
0xa9988419…9f45
0x34b655…2a6f
10 touches
10 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
8 touches
6 conflicts
0x1785cf5f…58ba
0x34b655…2a6f
8 touches
6 conflicts
0x23769ebc…c8ed
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
55 conflicts on slot 0x5f41438cce…d60d4f
Audit this contract →
← previous block·next block →recent activity