← previous blocknext block →recent activity
Analyzing
Block #102,221,438
23 transactions · 22 stateful · 2026-09-05 15:34:11 UTC
Parallelism
52/100
Blocked
50%
Avg conflicts / tx
2.22
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #102,221,438 · 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
1w02w13w04w07w18w09w210w311w416w517w618w719w821w922w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
20 touches
45 conflicts
0x20b94f7c…2a9b
0x34b655…2a6f
18 touches
36 conflicts
0xc824469a…6425
0x34b655…2a6f
16 touches
28 conflicts
0xfe39a1f7…8eb0
0x34b655…2a6f
10 touches
10 conflicts
0xd66696e0…0842
0x34b655…2a6f
10 touches
10 conflicts
0xe21a94dd…4838
0x34b655…2a6f
9 touches
10 conflicts
0x3bc232cc…9304
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…641f
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
45 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity