← previous blocknext block →recent activity
Analyzing
Block #76,526,577
10 transactions · 8 stateful · 2026-05-23 17:56:51 UTC
Parallelism
80/100
Blocked
38%
Avg conflicts / tx
0.3
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #76,526,577 · 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
1w02w13w14w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4036e360…62b1
0x065c9d…c394
4 touches
1 conflict
0x99a21305…dffc
0x2a68ba…90c5
4 touches
1 conflict
0x95523e2a…4c01
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x1b4010dc…0bc0
0x065c9d…c394
2 touches
0 conflicts
0x5aee8cae…11ab
0x065c9d…c394
2 touches
0 conflicts
0x77ed432f…fa04
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
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 0x4036e36069…3762b1
Audit this contract →
← previous block·next block →recent activity