← previous blocknext block →recent activity
Analyzing
Block #77,184,359
18 transactions · 15 stateful · 2026-05-26 18:56:14 UTC
Parallelism
83/100
Blocked
27%
Avg conflicts / tx
0.28
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #77,184,359 · 18 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w18w212w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x95523e2a…4c01
0x065c9d…c394
4 touches
1 conflict
0xc51d3663…0f45
0xa6afd3…d132
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x99961b35…6f84
0xa6afd3…d132
3 touches
1 conflict
0x2b930a6d…eb3f
0xa6afd3…d132
3 touches
1 conflict
0xa4e3b3b1…0911
0x2a68ba…90c5
2 touches
0 conflicts
0xb3572c95…9c4a
0x2a68ba…90c5
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 0x95523e2aaf…734c01
Audit this contract →
← previous block·next block →recent activity