← previous blocknext block →recent activity
Analyzing
Block #76,465,895
8 transactions · 7 stateful · 2026-05-23 11:12:47 UTC
Parallelism
63/100
Blocked
29%
Avg conflicts / tx
0.25
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #76,465,895 · 8 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
1w02w13w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x18cf3003…51d1
0x065c9d…c394
4 touches
1 conflict
0xa4960986…726e
0x065c9d…c394
3 touches
1 conflict
0x8a2ba64d…85e3
0x0a4fcb…a602
2 touches
0 conflicts
0x8a2ba64d…85e9
0x0a4fcb…a602
2 touches
0 conflicts
0x8a2ba64d…85ea
0x0a4fcb…a602
2 touches
0 conflicts
0x8a2ba64d…85eb
0x0a4fcb…a602
2 touches
0 conflicts
0x6bd9b2de…7d72
0x0f2610…0edc
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