← previous blocknext block →recent activity
Analyzing
Block #77,236,878
16 transactions · 10 stateful · 2026-05-27 00:49:04 UTC
Parallelism
88/100
Blocked
10%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #77,236,878 · 16 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
1w02w04w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x95523e2a…4c01
0x065c9d…c394
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x1a93f669…cc73
0x065c9d…c394
2 touches
0 conflicts
0x290fa01c…e150
0x065c9d…c394
2 touches
0 conflicts
0xa93af4e9…fd04
0x065c9d…c394
2 touches
0 conflicts
0xb5baa38b…ab49
0x065c9d…c394
2 touches
0 conflicts
0xf0ac0642…3d6a
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity