← previous blocknext block →recent activity
Analyzing
Block #74,805,267
10 transactions · 8 stateful · 2026-05-15 18:27:41 UTC
Parallelism
80/100
Blocked
13%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,805,267 · 10 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x083ad6a1…6b04
0x065c9d…c394
4 touches
1 conflict
0x4d35837b…d5cc
0x065c9d…c394
3 touches
1 conflict
0xc9f7b60e…ee35
0x065c9d…c394
3 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x05566676…49be
0x065c9d…c394
2 touches
0 conflicts
0x18f997d7…c905
0x065c9d…c394
2 touches
0 conflicts
0x47b807a2…3307
0x065c9d…c394
2 touches
0 conflicts
0xa3639915…afe4
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
1 conflict on slot 0x083ad6a185…946b04
Audit this contract →
← previous block·next block →recent activity