← previous blocknext block →recent activity
Analyzing
Block #76,529,729
15 transactions · 15 stateful · 2026-05-23 18:17:46 UTC
Parallelism
80/100
Blocked
27%
Avg conflicts / tx
0.6
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #76,529,729 · 15 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w04w15w06w17w29w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x75d17fe1…81a4
0xa6afd3…d132
6 touches
3 conflicts
0x95523e2a…4c01
0x065c9d…c394
4 touches
1 conflict
0x99a21305…dffc
0x2a68ba…90c5
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x60f7fbaf…bd58
0x34b655…2a6f
4 touches
1 conflict
0x0335ae80…8414
0x8d66a4…3095
4 touches
1 conflict
0x17cd1479…00bb
0x8d66a4…3095
4 touches
1 conflict
0x8a35acfb…d1a0
0x8d66a4…3095
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: 0xa6afd386…b0d132
3 conflicts on slot 0x75d17fe1ad…2081a4
Audit this contract →
← previous block·next block →recent activity