← previous blocknext block →recent activity
Analyzing
Block #73,867,273
10 transactions · 9 stateful · 2026-05-11 10:11:43 UTC
Parallelism
60/100
Blocked
33%
Avg conflicts / tx
0.8
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #73,867,273 · 10 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
1w02w04w16w27w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x7f81fb82…633e
0x065c9d…c394
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x4559d094…f5e1
0x065c9d…c394
2 touches
0 conflicts
0x4e0b917b…9945
0x065c9d…c394
2 touches
0 conflicts
0x73e7a54d…0781
0x065c9d…c394
2 touches
0 conflicts
0xf8b759c9…3c98
0x065c9d…c394
2 touches
0 conflicts
0x30276c1c…47b4
0x2a68ba…90c5
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
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity