← previous blocknext block →recent activity
Analyzing
Block #76,157,943
11 transactions · 10 stateful · 2026-05-22 01:02:25 UTC
Parallelism
82/100
Blocked
20%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #76,157,943 · 11 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
1w02w13w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xf3d7a307…4d63
0x065c9d…c394
4 touches
1 conflict
0xfe2bac2b…2cec
0x065c9d…c394
4 touches
1 conflict
0x20fa183b…e154
0x065c9d…c394
2 touches
0 conflicts
0x3cefa5d2…7217
0x065c9d…c394
2 touches
0 conflicts
0x3e69ae73…9ccc
0x065c9d…c394
2 touches
0 conflicts
0x5081f205…1932
0x065c9d…c394
2 touches
0 conflicts
0x5a994cae…95d3
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