← previous blocknext block →recent activity
Analyzing
Block #73,752,897
10 transactions · 9 stateful · 2026-05-10 21:25:27 UTC
Parallelism
60/100
Blocked
44%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #73,752,897 · 10 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w04w15w26w39w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0x0ff45a52…e5da
0x065c9d…c394
4 touches
1 conflict
0xd360a80c…8f06
0x065c9d…c394
4 touches
1 conflict
0x8a2657f5…e008
0x34b655…2a6f
4 touches
1 conflict
0x1b79d794…1598
0x065c9d…c394
3 touches
1 conflict
0x974aef48…f5eb
0x065c9d…c394
3 touches
1 conflict
0x4d87512b…897c
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 0xf2f76ab392…f3623e
Audit this contract →
← previous block·next block →recent activity