← previous blocknext block →recent activity
Analyzing
Block #77,346,946
20 transactions · 19 stateful · 2026-05-27 13:02:45 UTC
Parallelism
75/100
Blocked
53%
Avg conflicts / tx
1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #77,346,946 · 20 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w15w26w38w010w111w212w313w414w015w116w417w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xab3526…fa38
10 touches
10 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
8 touches
6 conflicts
0x8d0d8061…d410
0xc8689a…ee79
6 touches
3 conflicts
0x5a409e7f…09b6
0x69df8a…6292
6 touches
3 conflicts
0x66d63204…51a0
0x69df8a…6292
6 touches
3 conflicts
0x7a12283f…b18a
0x69df8a…6292
6 touches
3 conflicts
0x00000000…003d
0x851145…3f07
6 touches
3 conflicts
0x1dedc384…ff57
0x851145…3f07
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: 0xab35264b…1cfa38
10 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity