← previous blocknext block →recent activity
Analyzing
Block #76,570,014
11 transactions · 8 stateful · 2026-05-23 22:46:13 UTC
Parallelism
82/100
Blocked
25%
Avg conflicts / tx
0.27
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #76,570,014 · 11 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
1w02w03w15w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0xdfa159d0…1576
0x065c9d…c394
4 touches
1 conflict
0x52063cc3…ea67
0x065c9d…c394
4 touches
1 conflict
0xd15dbe46…e9ed
0x065c9d…c394
3 touches
1 conflict
0x7eb74a8f…a23c
0x065c9d…c394
2 touches
0 conflicts
0xc35b9205…c5b0
0x065c9d…c394
2 touches
0 conflicts
0xf3884263…9212
0x065c9d…c394
2 touches
0 conflicts
0xfc99f100…f262
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 0xf2f76ab392…f3623e
Audit this contract →
← previous block·next block →recent activity