← previous blocknext block →recent activity
Analyzing
Block #77,351,033
8 transactions · 7 stateful · 2026-05-27 13:29:52 UTC
Parallelism
63/100
Blocked
43%
Avg conflicts / tx
0.5
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #77,351,033 · 8 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcdbf0bb…d041
0x065c9d…c394
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0xcc8faac2…c766
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xe18a6771…7104
0x065c9d…c394
3 touches
1 conflict
0x67f69549…efd3
0x065c9d…c394
3 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x75e53156…42f3
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
1 conflict on slot 0xbcdbf0bba6…86d041
Audit this contract →
← previous block·next block →recent activity