← previous blocknext block →recent activity
Analyzing
Block #76,550,672
15 transactions · 13 stateful · 2026-05-23 20:37:23 UTC
Parallelism
87/100
Blocked
23%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #76,550,672 · 15 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
3w06w09w111w113w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xdfa159d0…1576
0x065c9d…c394
4 touches
1 conflict
0x38538022…dac7
0xd32edf…ff58
3 touches
1 conflict
0x8f478f26…9d56
0x000000…012a
2 touches
0 conflicts
0xacdf1114…3f0a
0x065c9d…c394
2 touches
0 conflicts
0xc3006de0…9726
0x188d58…ea8e
2 touches
0 conflicts
0xc3006de0…9728
0x188d58…ea8e
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