← previous blocknext block →recent activity
Analyzing
Block #74,258,206
7 transactions · 7 stateful · 2026-05-13 05:35:20 UTC
Parallelism
57/100
Blocked
29%
Avg conflicts / tx
0.43
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #74,258,206 · 7 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
3w04w05w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x27f9a31c…9550
0x065c9d…c394
2 touches
0 conflicts
0x78edf516…3c2a
0x065c9d…c394
2 touches
0 conflicts
0xa10d0920…f763
0x065c9d…c394
2 touches
0 conflicts
0xb3edcc34…d086
0x065c9d…c394
2 touches
0 conflicts
0xcf3283ba…c9fa
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