← previous blocknext block →recent activity
Analyzing
Block #77,184,095
9 transactions · 7 stateful · 2026-05-26 18:54:28 UTC
Parallelism
67/100
Blocked
29%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #77,184,095 · 9 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
1w02w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x03632367…e560
0x065c9d…c394
2 touches
0 conflicts
0x0aa86c1b…0111
0x065c9d…c394
2 touches
0 conflicts
0x1b2d9128…0c04
0x065c9d…c394
2 touches
0 conflicts
0x1c771cfd…1383
0x065c9d…c394
2 touches
0 conflicts
0x60df6b53…0a1a
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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity