← previous blocknext block →recent activity
Analyzing
Block #77,308,188
8 transactions · 7 stateful · 2026-05-27 08:44:45 UTC
Parallelism
50/100
Blocked
43%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #77,308,188 · 8 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
1w02w13w24w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x6082814c…d39b
0x754704…b603
2 touches
1 conflict
0x5297b8eb…1b91
0x2a68ba…90c5
2 touches
1 conflict
0x066ffa80…d663
0x065c9d…c394
2 touches
0 conflicts
0x3480478e…62a0
0x065c9d…c394
2 touches
0 conflicts
0x77ed432f…fa04
0x065c9d…c394
2 touches
0 conflicts
0x891d12ea…feac
0x065c9d…c394
2 touches
0 conflicts
0xa28c3ff2…08ec
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
1 conflict on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity