← previous blocknext block →recent activity
Analyzing
Block #77,239,526
9 transactions · 8 stateful · 2026-05-27 01:06:45 UTC
Parallelism
56/100
Blocked
38%
Avg conflicts / tx
0.67
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #77,239,526 · 9 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w16w28w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x77ed432f…fa04
0x065c9d…c394
6 touches
3 conflicts
0xa7313e3d…abe6
0x065c9d…c394
3 touches
1 conflict
0x066ffa80…d663
0x065c9d…c394
2 touches
0 conflicts
0x16063e3d…60e6
0x065c9d…c394
2 touches
0 conflicts
0x30323eba…47e7
0x065c9d…c394
2 touches
0 conflicts
0x3dc5a3e3…2dc8
0x065c9d…c394
2 touches
0 conflicts
0x8d02a9a8…fb31
0x065c9d…c394
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-MON/USDC
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity