← previous blocknext block →recent activity
Analyzing
Block #73,477,988
8 transactions · 7 stateful · 2026-05-09 14:44:51 UTC
Parallelism
75/100
Blocked
29%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #73,477,988 · 8 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
1w04w16w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6f08361d…bda6
0x065c9d…c394
4 touches
1 conflict
0x16028694…d720
0x34b655…2a6f
4 touches
1 conflict
0xa15427f6…d932
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x4710390d…6040
0x065c9d…c394
2 touches
0 conflicts
0x8f61f264…a9ce
0x065c9d…c394
2 touches
0 conflicts
0x9dc69c2f…00f1
0x065c9d…c394
2 touches
0 conflicts
0xaf370227…f180
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
1 conflict on slot 0x6f08361da9…89bda6
Audit this contract →
← previous block·next block →recent activity