← previous blocknext block →recent activity
Analyzing
Block #76,146,395
6 transactions · 5 stateful · 2026-05-21 23:45:25 UTC
Parallelism
67/100
Blocked
40%
Avg conflicts / tx
0.33
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #76,146,395 · 6 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
0xf3d7a307…4d63
0x065c9d…c394
4 touches
1 conflict
0x99a21305…dffc
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x3c6b78fa…d889
0x065c9d…c394
2 touches
0 conflicts
0x817ddf5c…edb0
0x065c9d…c394
2 touches
0 conflicts
0xed788a02…a864
0x065c9d…c394
2 touches
0 conflicts
0xfe2bac2b…2cec
0x065c9d…c394
2 touches
0 conflicts
0x06e40499…165e
0x1d1325…2305
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 0xf3d7a307cc…f14d63
Audit this contract →
← previous block·next block →recent activity