← previous blocknext block →recent activity
Analyzing
Block #76,470,525
8 transactions · 6 stateful · 2026-05-23 11:43:43 UTC
Parallelism
75/100
Blocked
33%
Avg conflicts / tx
0.38
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #76,470,525 · 8 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
1w02w03w14w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x18cf3003…51d1
0x065c9d…c394
4 touches
1 conflict
0x2bd34b59…5b6e
0x065c9d…c394
3 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x07cf2c2d…fe93
0x065c9d…c394
2 touches
0 conflicts
0x27a04273…27c5
0x065c9d…c394
2 touches
0 conflicts
0xcc8faac2…c766
0x065c9d…c394
2 touches
0 conflicts
0xf9654e08…0f8a
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
1 conflict on slot 0x046a928e85…e50012
Audit this contract →
← previous block·next block →recent activity