← previous blocknext block →recent activity
Analyzing
Block #76,346,769
11 transactions · 9 stateful · 2026-05-22 21:59:26 UTC
Parallelism
73/100
Blocked
44%
Avg conflicts / tx
0.73
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #76,346,769 · 11 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
1w02w03w04w15w17w28w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x75d17fe1…81a4
0xa6afd3…d132
6 touches
3 conflicts
0xb24a9fb5…f3d7
0xa6afd3…d132
6 touches
3 conflicts
0xe8aab7db…a319
0xa6afd3…d132
4 touches
1 conflict
0xc626ebb8…c82f
0x065c9d…c394
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0019
0x1b6862…e19c
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