← previous blocknext block →recent activity
Analyzing
Block #73,676,447
14 transactions · 10 stateful · 2026-05-10 12:49:38 UTC
Parallelism
79/100
Blocked
20%
Avg conflicts / tx
0.21
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #73,676,447 · 14 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
1w010w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x0712f8c5…2b65
0x065c9d…c394
3 touches
1 conflict
0x82da1c54…94b2
0x065c9d…c394
3 touches
1 conflict
0x89875e0f…8a65
0x065c9d…c394
3 touches
1 conflict
0x25953640…c9ba
0x065c9d…c394
2 touches
0 conflicts
0x529acb6a…fcc6
0x065c9d…c394
2 touches
0 conflicts
0x7314433f…758b
0x065c9d…c394
2 touches
0 conflicts
0xf5e1dec0…fd45
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