← previous blocknext block →recent activity
Analyzing
Block #73,743,895
15 transactions · 14 stateful · 2026-05-10 20:24:42 UTC
Parallelism
33/100
Blocked
71%
Avg conflicts / tx
2.4
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #73,743,895 · 15 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w07w38w49w510w611w712w813w914w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
16 touches
28 conflicts
0x529acb6a…fcc6
0x065c9d…c394
8 touches
6 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
8 touches
6 conflicts
0x046a928e…0012
0x2a68ba…90c5
6 touches
3 conflicts
0x0ac31945…2c72
0x065c9d…c394
6 touches
3 conflicts
0xaa8a1c54…ead3
0x34b655…2a6f
4 touches
1 conflict
0xc2cd088e…5c82
0x065c9d…c394
4 touches
1 conflict
0xff8a8d59…4a48
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
28 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity