← previous blocknext block →recent activity
Analyzing
Block #73,753,678
17 transactions · 16 stateful · 2026-05-10 21:30:42 UTC
Parallelism
71/100
Blocked
63%
Avg conflicts / tx
1.18
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #73,753,678 · 17 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w06w18w29w310w411w012w113w215w216w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x15d039e7…4bb6
0x34b655…2a6f
6 touches
3 conflicts
0x046a928e…0012
0x2a68ba…90c5
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0x7f81fb82…633e
0x065c9d…c394
6 touches
3 conflicts
0xb159af88…a9e7
0x065c9d…c394
6 touches
3 conflicts
0x1a4b4152…0a08
0x6c4bfa…a540
4 touches
1 conflict
0x2e2214a9…fe0d
0x6c4bfa…a540
4 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