← previous blocknext block →recent activity
Analyzing
Block #73,868,329
11 transactions · 10 stateful · 2026-05-11 10:18:44 UTC
Parallelism
82/100
Blocked
10%
Avg conflicts / tx
0.09
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #73,868,329 · 11 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x685f2d16…dd56
0x065c9d…c394
3 touches
1 conflict
0x8ba33db5…261e
0x065c9d…c394
3 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x29d991ec…5a51
0x065c9d…c394
2 touches
0 conflicts
0x2a1e89b7…fa2a
0x065c9d…c394
2 touches
0 conflicts
0x3ca756d9…a40d
0x065c9d…c394
2 touches
0 conflicts
0xda74f314…cb7c
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