← previous blocknext block →recent activity
Analyzing
Block #73,680,070
12 transactions · 9 stateful · 2026-05-10 13:14:06 UTC
Parallelism
67/100
Blocked
33%
Avg conflicts / tx
0.75
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #73,680,070 · 12 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
6w07w08w19w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x046a928e…0012
0x2a68ba…90c5
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x529acb6a…fcc6
0x065c9d…c394
4 touches
1 conflict
0xf636ce02…213e
0x065c9d…c394
3 touches
1 conflict
0xe48b0689…4b3d
0x065c9d…c394
3 touches
1 conflict
0x711f909c…5df4
0x1efe02…37d6
2 touches
0 conflicts
0x8ff96f00…aab2
0x1efe02…37d6
2 touches
0 conflicts
0x00000000…0099
0xaa3145…feec
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
6 conflicts on slot 0x046a928e85…e50012
Audit this contract →
← previous block·next block →recent activity