← previous blocknext block →recent activity
Analyzing
Block #76,212,152
8 transactions · 7 stateful · 2026-05-22 07:03:00 UTC
Parallelism
63/100
Blocked
43%
Avg conflicts / tx
0.5
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #76,212,152 · 8 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
1w02w13w26w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x99a21305…dffc
0x2a68ba…90c5
6 touches
3 conflicts
0x10abefc9…c9bc
0x1d1325…2305
4 touches
1 conflict
0x10d80fee…dbda
0x1d1325…2305
4 touches
1 conflict
0x2f4b2cf9…4e1e
0x1d1325…2305
4 touches
1 conflict
0x3426dbed…d278
0x1d1325…2305
4 touches
1 conflict
0x3484c9df…bfd5
0x1d1325…2305
4 touches
1 conflict
0x595839b9…ca61
0x1d1325…2305
4 touches
1 conflict
0x5cc231f5…f1cd
0x1d1325…2305
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: Kuru Exchange: MarginAccount
3 conflicts on slot 0x99a2130578…57dffc
Audit this contract →
← previous block·next block →recent activity