← previous blocknext block →recent activity
Analyzing
Block #75,924,451
25 transactions · 23 stateful · 2026-05-20 23:06:50 UTC
Parallelism
68/100
Blocked
70%
Avg conflicts / tx
1.88
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #75,924,451 · 25 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
1w02w13w24w36w47w58w09w110w011w112w213w619w220w321w422w523w624w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5086c64a…28ba
0x34b655…2a6f
16 touches
28 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0xea02471d…1542
0x34b655…2a6f
10 touches
10 conflicts
0xc6ec142d…dd1e
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…0029
0x1b6862…e19c
8 touches
6 conflicts
0x75e73565…45f5
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x892daf6e…48d8
0x065c9d…c394
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
28 conflicts on slot 0x5086c64a56…bb28ba
Audit this contract →
← previous block·next block →recent activity