← previous blocknext block →recent activity
Analyzing
Block #76,550,756
28 transactions · 20 stateful · 2026-05-23 20:37:56 UTC
Parallelism
86/100
Blocked
35%
Avg conflicts / tx
0.39
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #76,550,756 · 28 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
1w02w04w17w112w013w117w018w119w221w222w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x35ea602c…019a
0x34b655…2a6f
6 touches
3 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
6 touches
3 conflicts
0x3df6fd4e…f4e1
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…001d
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002d
0x1b6862…e19c
4 touches
1 conflict
0x3af0dd8e…0026
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x10d80fee…dbda
0x1d1325…2305
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
3 conflicts on slot 0x35ea602c56…c2019a
Audit this contract →
← previous block·next block →recent activity