← previous blocknext block →recent activity
Analyzing
Block #73,743,964
22 transactions · 13 stateful · 2026-05-10 20:25:09 UTC
Parallelism
77/100
Blocked
54%
Avg conflicts / tx
0.59
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #73,743,964 · 22 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w09w010w112w115w116w217w318w421w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0x046a928e…0012
0x2a68ba…90c5
6 touches
3 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
4 touches
1 conflict
0x99db93cc…d61f
0x34b655…2a6f
4 touches
1 conflict
0xaa8a1c54…ead3
0x34b655…2a6f
4 touches
1 conflict
0x8a35acfb…d1ab
0x8d66a4…3095
3 touches
1 conflict
0xe89e1a22…ce49
0x8d66a4…3095
3 touches
1 conflict
0x8ee3639a…604f
0xd32edf…ff58
3 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
10 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity