← previous blocknext block →recent activity
Analyzing
Block #76,244,445
8 transactions · 8 stateful · 2026-05-22 10:38:32 UTC
Parallelism
50/100
Blocked
38%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #76,244,445 · 8 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xba38536d…2b7d
0x065c9d…c394
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x0f3d6629…d8e9
0x065c9d…c394
2 touches
0 conflicts
0x13f3511a…ea6a
0x065c9d…c394
2 touches
0 conflicts
0x348fda08…7e96
0x065c9d…c394
2 touches
0 conflicts
0x441cbd2e…1814
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 0xba38536db1…342b7d
Audit this contract →
← previous block·next block →recent activity