← previous blocknext block →recent activity
Analyzing
Block #102,443,163
23 transactions · 23 stateful · 2026-09-06 10:17:35 UTC
Parallelism
83/100
Blocked
39%
Avg conflicts / tx
0.74
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,443,163 · 23 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w29w010w011w112w215w116w217w318w019w020w121w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…641f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…642d
0x34b655…2a6f
8 touches
6 conflicts
0x0147266d…695a
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…641d
0x34b655…2a6f
8 touches
6 conflicts
0xbceecf11…0120
0x34b655…2a6f
6 touches
4 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0xea2d3331…6e34
0x1b6862…e19c
6 touches
3 conflicts
0x0b0bf18f…60ac
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
6 conflicts on slot 0xc824469a90…af641f
Audit this contract →
← previous block·next block →recent activity