← previous blocknext block →recent activity
Analyzing
Block #77,237,081
27 transactions · 19 stateful · 2026-05-27 00:50:25 UTC
Parallelism
78/100
Blocked
47%
Avg conflicts / tx
0.93
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #77,237,081 · 27 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w17w08w09w110w211w012w114w015w117w218w319w420w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0xca420493…9789
0xd32edf…ff58
9 touches
10 conflicts
0x95523e2a…4c01
0x065c9d…c394
8 touches
6 conflicts
0x77ed432f…fa04
0x065c9d…c394
8 touches
6 conflicts
0xe95ed14b…d431
0x065c9d…c394
7 touches
6 conflicts
0xf071b5c8…581b
0x065c9d…c394
7 touches
6 conflicts
0x4f75d6af…2d97
0x065c9d…c394
6 touches
3 conflicts
0x76669087…a4b8
0x065c9d…c394
6 touches
3 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
10 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity