← previous blocknext block →recent activity
Analyzing
Block #77,189,716
20 transactions · 12 stateful · 2026-05-26 19:32:02 UTC
Parallelism
80/100
Blocked
42%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #77,189,716 · 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
4w05w06w17w18w210w211w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x95523e2a…4c01
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0xd71a331e…42ea
0xa6afd3…d132
4 touches
1 conflict
0x4245e4e8…096e
0x000000…012a
2 touches
0 conflicts
0xbdae6a67…04a3
0x065c9d…c394
2 touches
0 conflicts
0x10abefc9…c9bc
0x1d1325…2305
2 touches
0 conflicts
0x10d80fee…dbda
0x1d1325…2305
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
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity