← previous blocknext block →recent activity
Analyzing
Block #77,182,294
15 transactions · 11 stateful · 2026-05-26 18:42:27 UTC
Parallelism
87/100
Blocked
18%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #77,182,294 · 15 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
1w02w03w14w1
- 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
0x77ed432f…fa04
0x065c9d…c394
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x11b4c24b…ec37
0x065c9d…c394
2 touches
0 conflicts
0x30c81696…e76b
0x065c9d…c394
2 touches
0 conflicts
0x5ff84dda…24cd
0x065c9d…c394
2 touches
0 conflicts
0x75723945…b8d5
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