← previous blocknext block →recent activity
Analyzing
Block #75,701,797
23 transactions · 17 stateful · 2026-05-19 22:22:39 UTC
Parallelism
83/100
Blocked
53%
Avg conflicts / tx
0.65
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #75,701,797 · 23 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w26w010w113w014w115w216w317w218w220w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
8 touches
6 conflicts
0xcc4f1f14…aa5f
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x00000000…0004
0x8d66a4…3095
6 touches
3 conflicts
0xe6455d1f…1029
0x754704…b603
6 touches
3 conflicts
0x0d0b2509…074d
0x3bd359…433a
6 touches
3 conflicts
0x674c1ed4…da3f
0x34b655…2a6f
6 touches
3 conflicts
0x3ec45668…8dbe
0xd32edf…ff58
5 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
6 conflicts on slot 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity