← previous blocknext block →recent activity
Analyzing
Block #77,237,405
13 transactions · 9 stateful · 2026-05-27 00:52:35 UTC
Parallelism
85/100
Blocked
22%
Avg conflicts / tx
0.15
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #77,237,405 · 13 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w17w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xda36a936…9c69
0xa6afd3…d132
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x99a21305…dffc
0x2a68ba…90c5
4 touches
1 conflict
0xc12e32b0…bfca
0xa6afd3…d132
3 touches
1 conflict
0x00f7e3b7…e017
0x188d58…ea8e
2 touches
0 conflicts
0x10abefc9…c9bc
0x1d1325…2305
2 touches
0 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
2 touches
0 conflicts
0x99f666e3…b2a2
0x3bd359…433a
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-WETH/USDC
1 conflict on slot 0xda36a93642…c39c69
Audit this contract →
← previous block·next block →recent activity