← previous blocknext block →recent activity
Analyzing
Block #77,352,291
46 transactions · 35 stateful · 2026-05-27 13:38:15 UTC
Parallelism
85/100
Blocked
63%
Avg conflicts / tx
1.46
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #77,352,291 · 46 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
1w02w03w110w211w312w413w014w115w216w334w435w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0x17606ba6…1b6e
0x754704…b603
12 touches
15 conflicts
0xcc6434bd…6d5c
0xa6afd3…d132
10 touches
10 conflicts
0xc906436c…b676
0xa6afd3…d132
10 touches
10 conflicts
0x00000000…003d
0xa6afd3…d132
10 touches
10 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
10 touches
10 conflicts
0x7da167c8…8887
0xd32edf…ff58
9 touches
10 conflicts
0xe75ce681…ba5f
0x188d58…ea8e
8 touches
6 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: Perpl
21 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity