← previous blocknext block →recent activity
Analyzing
Block #102,276,511
21 transactions · 19 stateful · 2026-09-05 20:13:23 UTC
Parallelism
81/100
Blocked
32%
Avg conflicts / tx
0.43
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,276,511 · 21 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
1w04w07w115w116w217w218w320w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xde07eb52…8ae5
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x6ea1896c…e06f
0x34b655…2a6f
4 touches
1 conflict
0x6ea1896c…e070
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x839c0c71…bada
0x34b655…2a6f
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
3 conflicts on slot 0xde07eb525e…2b8ae5
Audit this contract →
← previous block·next block →recent activity