← previous blocknext block →recent activity
Analyzing
Block #73,696,842
8 transactions · 7 stateful · 2026-05-10 15:07:08 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,696,842 · 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
2w03w15w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x529acb6a…fcc6
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x0ac31945…2c72
0x065c9d…c394
4 touches
1 conflict
0x5df02260…03cc
0x065c9d…c394
2 touches
0 conflicts
0x71f91a7e…aba2
0x065c9d…c394
2 touches
0 conflicts
0x77f9127f…2511
0x065c9d…c394
2 touches
0 conflicts
0x84b2c5ad…19d3
0x065c9d…c394
2 touches
0 conflicts
0xa23cd89b…d209
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 0x529acb6ad1…f0fcc6
Audit this contract →
← previous block·next block →recent activity