← previous blocknext block →recent activity
Analyzing
Block #73,807,667
7 transactions · 6 stateful · 2026-05-11 03:34:38 UTC
Parallelism
57/100
Blocked
33%
Avg conflicts / tx
0.43
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #73,807,667 · 7 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
1w02w15w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x4d87512b…897c
0x065c9d…c394
4 touches
1 conflict
0x20e3ef0c…26c7
0x065c9d…c394
2 touches
0 conflicts
0x5682ed43…47e5
0x065c9d…c394
2 touches
0 conflicts
0xb95e2f9e…10bc
0x065c9d…c394
2 touches
0 conflicts
0xc861f6cc…0091
0x065c9d…c394
2 touches
0 conflicts
0xe29841bd…3d7d
0x065c9d…c394
2 touches
0 conflicts
0xff360154…ef1e
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