← previous blocknext block →recent activity
Analyzing
Block #73,672,380
8 transactions · 7 stateful · 2026-05-10 12:22:06 UTC
Parallelism
50/100
Blocked
57%
Avg conflicts / tx
0.88
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #73,672,380 · 8 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
1w04w15w26w37w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0xa299b34d…b4fd
0x065c9d…c394
4 touches
1 conflict
0x0ac31945…2c72
0x065c9d…c394
4 touches
1 conflict
0x936b590b…0798
0x065c9d…c394
4 touches
1 conflict
0xf5d4b971…f65a
0x065c9d…c394
4 touches
1 conflict
0x3e4281f8…f9a6
0x065c9d…c394
3 touches
1 conflict
0x913ab4e2…03ce
0x065c9d…c394
3 touches
1 conflict
0xa3cf3a22…4f37
0x065c9d…c394
3 touches
1 conflict
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