← previous blocknext block →recent activity
Analyzing
Block #77,238,788
8 transactions · 7 stateful · 2026-05-27 01:01:48 UTC
Parallelism
50/100
Blocked
43%
Avg conflicts / tx
0.75
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #77,238,788 · 8 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
1w03w14w26w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x75723945…b8d5
0x065c9d…c394
4 touches
1 conflict
0x95523e2a…4c01
0x065c9d…c394
4 touches
1 conflict
0x2466f67b…3006
0x065c9d…c394
4 touches
1 conflict
0xc80a9a9c…6688
0x065c9d…c394
3 touches
1 conflict
0x4b8ef371…f031
0x065c9d…c394
3 touches
1 conflict
0x06e40499…165e
0x1d1325…2305
2 touches
0 conflicts
0x45f562b2…9294
0x1d1325…2305
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