← previous blocknext block →recent activity
Analyzing
Block #77,219,858
8 transactions · 6 stateful · 2026-05-26 22:54:37 UTC
Parallelism
75/100
Blocked
17%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #77,219,858 · 8 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5c596e70…de1a
0x065c9d…c394
4 touches
1 conflict
0xc2428b97…a53e
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x15edcd3f…1dea
0x065c9d…c394
3 touches
1 conflict
0x229fda53…5d4e
0x065c9d…c394
3 touches
1 conflict
0x2c7e6701…319d
0x065c9d…c394
3 touches
1 conflict
0xe4f9b2f7…020c
0x065c9d…c394
2 touches
0 conflicts
0x06e40499…165e
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
1 conflict on slot 0x5c596e7099…36de1a
Audit this contract →
← previous block·next block →recent activity