← previous blocknext block →recent activity
Analyzing
Block #77,782,244
59 transactions · 38 stateful · 2026-05-29 13:24:20 UTC
Parallelism
76/100
Blocked
68%
Avg conflicts / tx
2.12
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #77,782,244 · 59 txs across 14 waves · depth 14
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w121w022w123w224w325w428w029w131w232w333w434w535w636w747w548w449w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xab3526…fa38
28 touches
91 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
10 touches
10 conflicts
0x94c21920…5885
0xa6afd3…d132
8 touches
6 conflicts
0x40e31e14…c46c
0xa6afd3…d132
8 touches
6 conflicts
0xce827910…ff22
0x065c9d…c394
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
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: 0xab35264b…1cfa38
91 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity