← previous blocknext block →recent activity
Analyzing
Block #75,946,719
27 transactions · 24 stateful · 2026-05-21 01:35:04 UTC
Parallelism
37/100
Blocked
67%
Avg conflicts / tx
4.96
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #75,946,719 · 27 txs across 17 waves · depth 17
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
wave w14
wave w15
wave w16
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w36w47w58w69w710w811w912w1013w1114w1215w1316w1425w1526w16
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe54a1f6f…18f2
0x34b655…2a6f
32 touches
120 conflicts
0xc6417de0…2191
0xc8689a…ee79
30 touches
105 conflicts
0xbc3d6b37…2215
0x34b655…2a6f
28 touches
91 conflicts
0x4f483049…3cc7
0x34b655…2a6f
28 touches
91 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
28 touches
91 conflicts
0x7d169b18…0aed
0x34b655…2a6f
22 touches
55 conflicts
0x6eba5e7f…4b52
0x34b655…2a6f
22 touches
55 conflicts
0xf853eb8e…4027
0x34b655…2a6f
20 touches
45 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
120 conflicts on slot 0xe54a1f6fdd…7918f2
Audit this contract →
← previous block·next block →recent activity