← previous blocknext block →recent activity
Analyzing
Block #77,782,816
20 transactions · 14 stateful · 2026-05-29 13:28:10 UTC
Parallelism
80/100
Blocked
43%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #77,782,816 · 20 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w06w17w38w010w115w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0xce827910…ff22
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x52e69143…95ad
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x55ed4390…77d4
0xa6afd3…d132
4 touches
1 conflict
0x94c21920…5885
0xa6afd3…d132
4 touches
1 conflict
0x00000000…0002
0xab3526…fa38
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 0x13a54fa2d3…a35ae3
Audit this contract →
← previous block·next block →recent activity