← previous blocknext block →recent activity
Analyzing
Block #76,575,713
9 transactions · 7 stateful · 2026-05-23 23:24:06 UTC
Parallelism
78/100
Blocked
29%
Avg conflicts / tx
0.22
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #76,575,713 · 9 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1af7d55b…9c5e
0xa6afd3…d132
4 touches
1 conflict
0x222fc893…acc9
0xa6afd3…d132
4 touches
1 conflict
0x0a036541…ff3c
0xa6afd3…d132
3 touches
1 conflict
0x1802505e…ac62
0xa6afd3…d132
3 touches
1 conflict
0x2f4b2cf9…4e1e
0x1d1325…2305
2 touches
0 conflicts
0x3426dbed…d278
0x1d1325…2305
2 touches
0 conflicts
0x5cc231f5…f1cd
0x1d1325…2305
2 touches
0 conflicts
0x7aa91b8f…d070
0x1d1325…2305
2 touches
0 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: 0xa6afd386…b0d132
1 conflict on slot 0x1af7d55bb1…469c5e
Audit this contract →
← previous block·next block →recent activity