← previous blocknext block →recent activity
Analyzing
Block #102,744,748
33 transactions · 29 stateful · 2026-09-07 11:41:57 UTC
Parallelism
70/100
Blocked
62%
Avg conflicts / tx
1.61
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #102,744,748 · 33 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
1w02w13w25w07w08w111w212w114w216w317w419w529w630w731w832w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x002fed35…79fa
0x2a68ba…90c5
12 touches
15 conflicts
0x23c92c32…89c5
0x065c9d…c394
12 touches
15 conflicts
0x014e90b3…470f
0x34b655…2a6f
12 touches
15 conflicts
0xa1087a5c…66c4
0x754704…b603
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xa3edde75…ecc6
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity