← previous blocknext block →recent activity
Analyzing
Block #77,240,271
17 transactions · 16 stateful · 2026-05-27 01:11:46 UTC
Parallelism
82/100
Blocked
13%
Avg conflicts / tx
0.18
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #77,240,271 · 17 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
1w011w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x77ed432f…fa04
0x065c9d…c394
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x12fddd8f…85fd
0x065c9d…c394
2 touches
0 conflicts
0x8f5ab4c4…e67d
0x065c9d…c394
2 touches
0 conflicts
0xa2c28e91…1f34
0x065c9d…c394
2 touches
0 conflicts
0xd31be9be…5a4f
0x065c9d…c394
2 touches
0 conflicts
0xf8132559…256b
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