← previous blocknext block →recent activity
Analyzing
Block #76,441,373
10 transactions · 6 stateful · 2026-05-23 08:29:38 UTC
Parallelism
80/100
Blocked
33%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #76,441,373 · 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
1w02w13w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9bf064a6…4f04
0x2a68ba…90c5
4 touches
1 conflict
0xa73f7419…3cb8
0x065c9d…c394
4 touches
1 conflict
0xea862a56…34dd
0xd32edf…ff58
3 touches
1 conflict
0x00f7e3b7…e015
0x188d58…ea8e
2 touches
0 conflicts
0x00f7e3b7…e016
0x188d58…ea8e
2 touches
0 conflicts
0x696a27c8…5847
0x2a68ba…90c5
2 touches
0 conflicts
0xc5c4c1d1…2145
0x3bd359…433a
2 touches
0 conflicts
0x00000000…0003
0x5e60bc…fe22
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
1 conflict on slot 0x9bf064a6f8…394f04
Audit this contract →
← previous block·next block →recent activity