← previous blocknext block →recent activity
Analyzing
Block #76,245,160
8 transactions · 6 stateful · 2026-05-22 10:43:18 UTC
Parallelism
63/100
Blocked
33%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #76,245,160 · 8 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
1w02w13w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x20b1d957…d77b
0x065c9d…c394
4 touches
1 conflict
0x1235be47…a89e
0x065c9d…c394
4 touches
1 conflict
0x39504d4c…1a08
0x065c9d…c394
2 touches
0 conflicts
0x55e8ea86…7971
0x065c9d…c394
2 touches
0 conflicts
0x77d2c425…0af4
0x065c9d…c394
2 touches
0 conflicts
0xbe021397…da58
0x065c9d…c394
2 touches
0 conflicts
0xf0145965…1dcb
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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity