← previous blocknext block →recent activity
Analyzing
Block #75,523,893
23 transactions · 20 stateful · 2026-05-19 02:36:13 UTC
Parallelism
65/100
Blocked
60%
Avg conflicts / tx
1.43
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #75,523,893 · 23 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
1w02w04w05w06w17w210w111w212w313w114w417w318w419w520w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5086c64a…28ba
0x34b655…2a6f
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xad98dc08…361e
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…0019
0x1b6862…e19c
6 touches
3 conflicts
0xcb45d9d6…cb81
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x085df2c1…305a
0x34b655…2a6f
6 touches
3 conflicts
0x23d37d0a…a891
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
15 conflicts on slot 0x5086c64a56…bb28ba
Audit this contract →
← previous block·next block →recent activity