← previous blocknext block →recent activity
Analyzing
Block #73,990,163
17 transactions · 13 stateful · 2026-05-11 23:51:07 UTC
Parallelism
76/100
Blocked
38%
Avg conflicts / tx
0.71
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #73,990,163 · 17 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
2w04w15w27w011w112w313w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf537eaa0…73c8
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x765c236f…ff45
0x2a68ba…90c5
6 touches
3 conflicts
0x6f08361d…bda6
0x065c9d…c394
6 touches
3 conflicts
0x30276c1c…47b4
0x2a68ba…90c5
6 touches
3 conflicts
0xaa397836…f76c
0xd32edf…ff58
5 touches
3 conflicts
0xda2bf921…a419
0x065c9d…c394
4 touches
1 conflict
0xf95e05bc…877e
0x065c9d…c394
4 touches
1 conflict
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 0xf537eaa0c6…3873c8
Audit this contract →
← previous block·next block →recent activity