← previous blocknext block →recent activity
Analyzing
Block #73,673,134
8 transactions · 8 stateful · 2026-05-10 12:27:12 UTC
Parallelism
50/100
Blocked
38%
Avg conflicts / tx
0.75
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #73,673,134 · 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
1w04w15w26w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0ac31945…2c72
0x065c9d…c394
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0xbb65d83b…ca85
0x065c9d…c394
4 touches
1 conflict
0x37dae668…185f
0x065c9d…c394
3 touches
1 conflict
0x1bd1124c…b9d3
0x065c9d…c394
3 touches
1 conflict
0x529acb6a…fcc6
0x065c9d…c394
2 touches
0 conflicts
0x7f81fb82…633e
0x065c9d…c394
2 touches
0 conflicts
0xa98f6e66…60a5
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: Market-MON/USDC
3 conflicts on slot 0x0ac3194537…8f2c72
Audit this contract →
← previous block·next block →recent activity