← previous blocknext block →recent activity
Analyzing
Block #79,123,139
40 transactions · 34 stateful · 2026-06-04 18:26:45 UTC
Parallelism
80/100
Blocked
47%
Avg conflicts / tx
1.27
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #79,123,139 · 40 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w110w011w112w213w314w418w019w120w221w422w024w531w032w133w238w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
10 touches
10 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0xb4c35fcd…43ae
0xa6afd3…d132
8 touches
6 conflicts
0x59ef13ba…2741
0x34b655…2a6f
8 touches
6 conflicts
0x41e8f1e0…7156
0xd32edf…ff58
7 touches
6 conflicts
0xf853eb8e…4027
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
28 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity