← previous blocknext block →recent activity
Analyzing
Block #73,686,948
8 transactions · 7 stateful · 2026-05-10 14:00:29 UTC
Parallelism
63/100
Blocked
29%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #73,686,948 · 8 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
2w06w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x0ac31945…2c72
0x065c9d…c394
4 touches
1 conflict
0x5239b87e…a357
0x065c9d…c394
3 touches
1 conflict
0x3c29d70e…8d2e
0x065c9d…c394
3 touches
1 conflict
0x7d85eabb…4785
0x065c9d…c394
2 touches
0 conflicts
0x91ca2b02…d9f2
0x065c9d…c394
2 touches
0 conflicts
0x9febc557…93ef
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity