← previous blocknext block →recent activity
Analyzing
Block #75,523,518
63 transactions · 34 stateful · 2026-05-19 02:33:38 UTC
Parallelism
87/100
Blocked
65%
Avg conflicts / tx
0.9
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #75,523,518 · 63 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
1w02w13w25w07w38w09w316w117w219w320w425w026w133w435w436w537w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5086c64a…28ba
0x34b655…2a6f
14 touches
21 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x0d0b2509…074d
0x3bd359…433a
10 touches
10 conflicts
0x4546ebad…b908
0x34b655…2a6f
10 touches
10 conflicts
0xe6455d1f…1029
0x754704…b603
10 touches
10 conflicts
0xbb80bfed…80bf
0x34b655…2a6f
10 touches
10 conflicts
0x892daf6e…48d8
0x065c9d…c394
8 touches
6 conflicts
0xea02471d…1542
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 0x5086c64a56…bb28ba
Audit this contract →
← previous block·next block →recent activity