← previous blocknext block →recent activity
Analyzing
Block #75,741,981
23 transactions · 18 stateful · 2026-05-20 02:50:15 UTC
Parallelism
70/100
Blocked
56%
Avg conflicts / tx
1.35
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #75,741,981 · 23 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w49w010w111w212w320w421w522w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf853eb8e…4027
0x34b655…2a6f
14 touches
21 conflicts
0x7cbd466f…1700
0x34b655…2a6f
12 touches
15 conflicts
0x1c913164…5c2e
0x34b655…2a6f
12 touches
15 conflicts
0x8d47c9a4…f11f
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
10 touches
10 conflicts
0x365da26c…fb02
0xd32edf…ff58
9 touches
10 conflicts
0x908d4442…2c4b
0x34b655…2a6f
8 touches
6 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
21 conflicts on slot 0xf853eb8e72…d84027
Audit this contract →
← previous block·next block →recent activity