← previous blocknext block →recent activity
Analyzing
Block #75,516,870
22 transactions · 16 stateful · 2026-05-19 01:48:05 UTC
Parallelism
73/100
Blocked
44%
Avg conflicts / tx
0.86
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #75,516,870 · 22 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
1w05w17w08w19w210w311w412w521w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
12 touches
15 conflicts
0x0175b1f6…af86
0x34b655…2a6f
8 touches
6 conflicts
0x8a35acfb…d1ac
0x8d66a4…3095
8 touches
6 conflicts
0x8a35acfb…d1ab
0x8d66a4…3095
8 touches
6 conflicts
0x4f4bdabd…ffba
0x34b655…2a6f
6 touches
3 conflicts
0x664bf99e…0a8c
0x34b655…2a6f
6 touches
3 conflicts
0x791d57e2…b2e0
0x34b655…2a6f
6 touches
3 conflicts
0x7a0e62a3…37f5
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 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity