← previous blocknext block →recent activity
Analyzing
Block #76,550,709
31 transactions · 22 stateful · 2026-05-23 20:37:37 UTC
Parallelism
90/100
Blocked
41%
Avg conflicts / tx
0.48
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #76,550,709 · 31 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
1w02w14w08w114w015w117w218w020w021w022w124w125w026w229w130w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3199a6b2…eb67
0xa6afd3…d132
6 touches
3 conflicts
0xc3c8642a…7da5
0x2a68ba…90c5
6 touches
3 conflicts
0x12a285ae…41c2
0x065c9d…c394
5 touches
3 conflicts
0x6ae2e113…812f
0xd32edf…ff58
5 touches
3 conflicts
0xd77e90ec…8c04
0x3bd359…433a
4 touches
1 conflict
0x08943ea2…ed03
0x754704…b603
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x0335ae80…8414
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 0x3199a6b20c…1aeb67
Audit this contract →
← previous block·next block →recent activity