← previous blocknext block →recent activity
Analyzing
Block #75,840,909
33 transactions · 27 stateful · 2026-05-20 13:49:36 UTC
Parallelism
76/100
Blocked
63%
Avg conflicts / tx
1.27
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #75,840,909 · 33 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
1w02w13w24w35w07w09w110w415w117w018w119w220w322w423w524w627w328w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5648d337…a780
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x3f89bdec…484e
0xd32edf…ff58
9 touches
10 conflicts
0x5f77d607…2c84
0x065c9d…c394
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
8 touches
6 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
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
10 conflicts on slot 0x5648d337b4…c4a780
Audit this contract →
← previous block·next block →recent activity