← previous blocknext block →recent activity
Analyzing
Block #76,476,560
12 transactions · 11 stateful · 2026-05-23 12:23:50 UTC
Parallelism
75/100
Blocked
27%
Avg conflicts / tx
0.42
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #76,476,560 · 12 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
1w02w03w14w05w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x0bd261be…21c6
0xa6afd3…d132
4 touches
1 conflict
0x27a04273…27c5
0x065c9d…c394
2 touches
0 conflicts
0x6a771e77…37e7
0x065c9d…c394
2 touches
0 conflicts
0x6f1f296a…3a49
0x065c9d…c394
2 touches
0 conflicts
0x961c0278…c736
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: MarginAccount
3 conflicts on slot 0xf2f76ab392…f3623e
Audit this contract →
← previous block·next block →recent activity