← previous blocknext block →recent activity
Analyzing
Block #73,571,838
9 transactions · 9 stateful · 2026-05-10 01:08:41 UTC
Parallelism
67/100
Blocked
22%
Avg conflicts / tx
0.56
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #73,571,838 · 9 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w06w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xc857dbd9…506a
0x065c9d…c394
4 touches
1 conflict
0x4d87512b…897c
0x065c9d…c394
4 touches
1 conflict
0x8577dca5…b7d6
0x065c9d…c394
3 touches
1 conflict
0x7d1a56d7…4c3f
0x065c9d…c394
3 touches
1 conflict
0x4048db89…30c3
0x34b655…2a6f
2 touches
0 conflicts
0x8c315b05…51c7
0x34b655…2a6f
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