← previous blocknext block →recent activity
Analyzing
Block #77,183,581
10 transactions · 8 stateful · 2026-05-26 18:51:03 UTC
Parallelism
60/100
Blocked
38%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #77,183,581 · 10 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
1w02w13w28w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6b3067f6…24ff
0x065c9d…c394
4 touches
2 conflicts
0x77ed432f…fa04
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x7469e9de…bfd7
0x065c9d…c394
3 touches
1 conflict
0x321b9f87…2d70
0x065c9d…c394
2 touches
0 conflicts
0x72026526…2c7d
0x065c9d…c394
2 touches
0 conflicts
0x75723945…b8d5
0x065c9d…c394
2 touches
0 conflicts
0x95523e2a…4c01
0x065c9d…c394
2 touches
0 conflicts
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: Market-MON/USDC
2 conflicts on slot 0x6b3067f6c0…9824ff
Audit this contract →
← previous block·next block →recent activity