← previous blocknext block →recent activity
Analyzing
Block #75,268,780
10 transactions · 7 stateful · 2026-05-17 22:03:04 UTC
Parallelism
70/100
Blocked
29%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #75,268,780 · 10 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
1w03w05w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x765c236f…ff45
0x2a68ba…90c5
6 touches
3 conflicts
0xfe2bac2b…2cec
0x065c9d…c394
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x064e1ed4…b864
0xd32edf…ff58
3 touches
1 conflict
0x3f27fcf4…4e42
0x065c9d…c394
3 touches
1 conflict
0x7e5b57ac…23db
0x065c9d…c394
2 touches
0 conflicts
0x99b8ac88…59a4
0x065c9d…c394
2 touches
0 conflicts
0xa65441a0…d631
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 0x765c236f2d…b5ff45
Audit this contract →
← previous block·next block →recent activity