← previous blocknext block →recent activity
Analyzing
Block #75,839,104
27 transactions · 22 stateful · 2026-05-20 13:37:29 UTC
Parallelism
78/100
Blocked
59%
Avg conflicts / tx
0.78
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #75,839,104 · 27 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
1w02w13w25w16w211w012w113w214w015w116w317w221w022w124w325w426w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1c913164…5c2e
0x34b655…2a6f
8 touches
6 conflicts
0x5f13dfe3…9360
0xd32edf…ff58
7 touches
6 conflicts
0xe75ce681…ba5f
0x188d58…ea8e
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001f
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002f
0x1b6862…e19c
6 touches
3 conflicts
0xb6d6d740…e921
0x1b6862…e19c
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
6 conflicts on slot 0x1c913164f5…845c2e
Audit this contract →
← previous block·next block →recent activity