← previous blocknext block →recent activity
Analyzing
Block #76,227,208
9 transactions · 7 stateful · 2026-05-22 08:43:40 UTC
Parallelism
78/100
Blocked
14%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #76,227,208 · 9 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
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x676bbc9e…a01e
0x065c9d…c394
4 touches
1 conflict
0x36139100…e944
0x065c9d…c394
3 touches
1 conflict
0x428ef176…8108
0x065c9d…c394
3 touches
1 conflict
0x0f3545ef…bed9
0x065c9d…c394
2 touches
0 conflicts
0x2c74dd0d…4306
0x065c9d…c394
2 touches
0 conflicts
0x749c70f7…1c23
0x065c9d…c394
2 touches
0 conflicts
0xec0ecded…cf29
0x065c9d…c394
2 touches
0 conflicts
0xf11c8f28…8a0b
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 0x676bbc9e11…f4a01e
Audit this contract →
← previous block·next block →recent activity