← previous blocknext block →recent activity
Analyzing
Block #76,104,329
16 transactions · 13 stateful · 2026-05-21 19:05:13 UTC
Parallelism
81/100
Blocked
38%
Avg conflicts / tx
0.31
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #76,104,329 · 16 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
1w03w04w16w17w28w211w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x99a21305…dffc
0x2a68ba…90c5
4 touches
1 conflict
0x247d3d81…6084
0x2c4667…b389
4 touches
1 conflict
0x00000000…0002
0xab3526…fa38
4 touches
1 conflict
0x41755291…977f
0x065c9d…c394
4 touches
1 conflict
0xe55a330f…5b2a
0x065c9d…c394
2 touches
0 conflicts
0x1f5a2e2b…65f1
0x1d1325…2305
2 touches
0 conflicts
0x8488f10f…9354
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity