← previous blocknext block →recent activity
Analyzing
Block #77,433,813
10 transactions · 8 stateful · 2026-05-27 22:41:21 UTC
Parallelism
80/100
Blocked
25%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #77,433,813 · 10 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
2w03w14w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x99754bf9…f739
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0xb3d35f8c…0456
0x065c9d…c394
3 touches
1 conflict
0x9238a31c…fcbd
0x065c9d…c394
2 touches
0 conflicts
0xa13c8c31…abae
0x065c9d…c394
2 touches
0 conflicts
0xb25eb2d2…3770
0x065c9d…c394
2 touches
0 conflicts
0xf05a9fbb…acdd
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 0x99754bf966…5ff739
Audit this contract →
← previous block·next block →recent activity