← previous blocknext block →recent activity
Analyzing
Block #75,702,991
13 transactions · 11 stateful · 2026-05-19 22:30:38 UTC
Parallelism
46/100
Blocked
64%
Avg conflicts / tx
1.69
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #75,702,991 · 13 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w06w18w29w310w411w512w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1c913164…5c2e
0x34b655…2a6f
14 touches
21 conflicts
0xf853eb8e…4027
0x34b655…2a6f
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xac8e97a0…8426
0x34b655…2a6f
6 touches
3 conflicts
0xf763cad4…23f1
0x34b655…2a6f
6 touches
3 conflicts
0x6d0c65d9…c36f
0x34b655…2a6f
6 touches
3 conflicts
0x50059a18…9b7b
0x34b655…2a6f
6 touches
3 conflicts
0x55b6a001…1e7a
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
21 conflicts on slot 0x1c913164f5…845c2e
Audit this contract →
← previous block·next block →recent activity