← previous blocknext block →recent activity
Analyzing
Block #75,839,126
28 transactions · 20 stateful · 2026-05-20 13:37:38 UTC
Parallelism
79/100
Blocked
50%
Avg conflicts / tx
0.82
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #75,839,126 · 28 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
5w06w08w09w110w211w313w114w115w217w319w025w326w427w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x32ead371…df4e
0xd32edf…ff58
7 touches
6 conflicts
0x1c913164…5c2e
0x34b655…2a6f
6 touches
3 conflicts
0xadb553c0…430a
0x34b655…2a6f
6 touches
3 conflicts
0x081dda3d…4b0e
0x34b655…2a6f
4 touches
1 conflict
0x23a320fb…cbd7
0x34b655…2a6f
4 touches
1 conflict
0x27bb29d3…842e
0x34b655…2a6f
4 touches
1 conflict
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