← previous blocknext block →recent activity
Analyzing
Block #77,237,135
14 transactions · 12 stateful · 2026-05-27 00:50:47 UTC
Parallelism
79/100
Blocked
17%
Avg conflicts / tx
0.43
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #77,237,135 · 14 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
1w02w03w04w15w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x95523e2a…4c01
0x065c9d…c394
6 touches
3 conflicts
0xf12476b3…15db
0x065c9d…c394
4 touches
2 conflicts
0x77ed432f…fa04
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x35f670b5…0d9b
0x065c9d…c394
3 touches
1 conflict
0xfdaeec49…3cd2
0x065c9d…c394
3 touches
1 conflict
0x58553ed4…22bb
0x065c9d…c394
3 touches
1 conflict
0x6416bad4…5aa3
0x065c9d…c394
3 touches
1 conflict
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 0x95523e2aaf…734c01
Audit this contract →
← previous block·next block →recent activity