← previous blocknext block →recent activity
Analyzing
Block #75,730,840
38 transactions · 30 stateful · 2026-05-20 01:36:09 UTC
Parallelism
63/100
Blocked
57%
Avg conflicts / tx
1.63
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #75,730,840 · 38 txs across 14 waves · depth 14
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w17w28w09w011w313w014w115w216w317w418w519w622w131w732w833w934w1035w1136w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
14 touches
21 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0x422d5490…52d9
0x34b655…2a6f
12 touches
15 conflicts
0x9e719c7a…df63
0x34b655…2a6f
8 touches
6 conflicts
0x0d622e34…0000
0x681e90…ae09
8 touches
6 conflicts
0x8a35acfb…d1a6
0x8d66a4…3095
8 touches
6 conflicts
0xe5e7089a…fb91
0x34b655…2a6f
6 touches
3 conflicts
0xeb5b61a2…b2bc
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 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity