← previous blocknext block →recent activity
Analyzing
Block #73,971,147
8 transactions · 7 stateful · 2026-05-11 21:43:16 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,971,147 · 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
2w03w14w2
- 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
0x1f73c057…da40
0x065c9d…c394
2 touches
0 conflicts
0x4083ca0f…f229
0x065c9d…c394
2 touches
0 conflicts
0x4846a9da…66c5
0x065c9d…c394
2 touches
0 conflicts
0x4e7c6053…7d9b
0x065c9d…c394
2 touches
0 conflicts
0x66b22887…0d7a
0x065c9d…c394
2 touches
0 conflicts
0xec4d7651…edc0
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