← previous blocknext block →recent activity
Analyzing
Block #76,448,698
10 transactions · 7 stateful · 2026-05-23 09:18:19 UTC
Parallelism
80/100
Blocked
29%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #76,448,698 · 10 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
1w04w16w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xd833bd71…3525
0x34b655…2a6f
4 touches
1 conflict
0xf9b8ae99…32b3
0x34b655…2a6f
4 touches
1 conflict
0x70073345…8836
0x065c9d…c394
2 touches
0 conflicts
0x76af8bce…b112
0x065c9d…c394
2 touches
0 conflicts
0x9cbdd3fb…ea22
0x065c9d…c394
2 touches
0 conflicts
0xe91e6841…a87f
0x065c9d…c394
2 touches
0 conflicts
0xf5f84647…3e0c
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity