← previous blocknext block →recent activity
Analyzing
Block #73,688,493
10 transactions · 9 stateful · 2026-05-10 14:10:54 UTC
Parallelism
60/100
Blocked
33%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #73,688,493 · 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
1w04w15w26w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x529acb6a…fcc6
0x065c9d…c394
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x046a928e…0012
0x2a68ba…90c5
6 touches
3 conflicts
0x0ac31945…2c72
0x065c9d…c394
2 touches
0 conflicts
0x4a91cb71…d106
0x065c9d…c394
2 touches
0 conflicts
0x5c409aa9…0804
0x065c9d…c394
2 touches
0 conflicts
0x8e01f2bc…8a69
0x065c9d…c394
2 touches
0 conflicts
0xb0b2ada3…f640
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
6 conflicts on slot 0x529acb6ad1…f0fcc6
Audit this contract →
← previous block·next block →recent activity