← previous blocknext block →recent activity
Analyzing
Block #106,932,028
32 transactions · 32 stateful · 2026-09-22 03:48:57 UTC
Parallelism
69/100
Blocked
56%
Avg conflicts / tx
1.81
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #106,932,028 · 32 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
6w07w18w29w010w111w212w313w414w515w016w117w218w319w420w521w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x70986451…c6bd
0x34b655…2a6f
18 touches
36 conflicts
0xccebf5c5…8758
0x34b655…2a6f
16 touches
28 conflicts
0x251ee419…4404
0x34b655…2a6f
16 touches
28 conflicts
0x42522e76…2592
0x34b655…2a6f
12 touches
15 conflicts
0x7462b8f2…6312
0x34b655…2a6f
12 touches
15 conflicts
0x7fa77195…d46f
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…004b
0x80c745…7210
6 touches
3 conflicts
0x94e7f277…471b
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
36 conflicts on slot 0x7098645134…3ac6bd
Audit this contract →
← previous block·next block →recent activity