← previous blocknext block →recent activity
Analyzing
Block #102,290,115
21 transactions · 17 stateful · 2026-09-05 21:22:20 UTC
Parallelism
71/100
Blocked
59%
Avg conflicts / tx
0.86
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #102,290,115 · 21 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w15w26w37w411w212w314w517w018w119w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3c67d31e…3dbe
0x34b655…2a6f
8 touches
6 conflicts
0x61b7c7e7…6199
0xd32edf…ff58
7 touches
6 conflicts
0x88bfd4c1…3190
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
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
6 conflicts on slot 0x3c67d31e03…f03dbe
Audit this contract →
← previous block·next block →recent activity