← previous blocknext block →recent activity
Analyzing
Block #73,968,245
12 transactions · 10 stateful · 2026-05-11 21:23:51 UTC
Parallelism
67/100
Blocked
40%
Avg conflicts / tx
0.67
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #73,968,245 · 12 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
1w02w13w24w38w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x6f08361d…bda6
0x065c9d…c394
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x68b1ae0a…d107
0x065c9d…c394
2 touches
0 conflicts
0x71de8dd3…9ca7
0x065c9d…c394
2 touches
0 conflicts
0xc10ceaa2…3c7d
0x065c9d…c394
2 touches
0 conflicts
0xeb1af794…8bb0
0x065c9d…c394
2 touches
0 conflicts
0xf537eaa0…73c8
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity