← previous blocknext block →recent activity
Analyzing
Block #77,184,983
30 transactions · 25 stateful · 2026-05-26 19:00:25 UTC
Parallelism
73/100
Blocked
48%
Avg conflicts / tx
1.33
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #77,184,983 · 30 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w16w17w010w211w012w214w315w416w517w418w623w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
12 touches
15 conflicts
0x99a21305…dffc
0x2a68ba…90c5
10 touches
10 conflicts
0x77ed432f…fa04
0x065c9d…c394
10 touches
10 conflicts
0x95523e2a…4c01
0x065c9d…c394
10 touches
10 conflicts
0x1fff6dcb…b3f4
0xc8689a…ee79
6 touches
3 conflicts
0x55db53f1…7e8a
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
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
15 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity