← previous blocknext block →recent activity
Analyzing
Block #75,518,165
19 transactions · 16 stateful · 2026-05-19 01:56:54 UTC
Parallelism
68/100
Blocked
63%
Avg conflicts / tx
1.26
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #75,518,165 · 19 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w36w38w09w414w115w216w317w418w5
- 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
0x99aa63e0…42de
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…0019
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0029
0x1b6862…e19c
6 touches
3 conflicts
0x0a85a226…83bb
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x5f77d607…2c84
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
15 conflicts on slot 0x5086c64a56…bb28ba
Audit this contract →
← previous block·next block →recent activity