← previous blocknext block →recent activity
Analyzing
Block #77,526,889
30 transactions · 26 stateful · 2026-05-28 09:01:20 UTC
Parallelism
77/100
Blocked
54%
Avg conflicts / tx
1.17
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #77,526,889 · 30 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w17w08w19w210w011w112w213w014w115w216w317w418w519w621w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xab3526…fa38
14 touches
21 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0xcbd23469…a4df
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…000b
0x90c374…be45
6 touches
3 conflicts
0x00000000…000a
0x90c374…be45
6 touches
3 conflicts
0x7d167522…b840
0xd32edf…ff58
5 touches
3 conflicts
0xba5743c7…21c0
0x1b6862…e19c
4 touches
1 conflict
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
21 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity