← previous blocknext block →recent activity
Analyzing
Block #76,569,845
17 transactions · 12 stateful · 2026-05-23 22:45:05 UTC
Parallelism
71/100
Blocked
42%
Avg conflicts / tx
0.82
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #76,569,845 · 17 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w15w26w37w49w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0xb3572c95…9c4a
0x2a68ba…90c5
6 touches
3 conflicts
0x222fc893…acc9
0xa6afd3…d132
6 touches
3 conflicts
0x1af7d55b…9c5e
0xa6afd3…d132
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0xc0d22fd1…62a7
0xa6afd3…d132
3 touches
1 conflict
0x5c3df96c…e810
0xa6afd3…d132
3 touches
1 conflict
0xb3432792…ed94
0xa6afd3…d132
3 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
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity