← previous blocknext block →recent activity
Analyzing
Block #74,385,697
7 transactions · 6 stateful · 2026-05-13 19:43:26 UTC
Parallelism
71/100
Blocked
17%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,385,697 · 7 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
1w04w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3cbb6794…ff13
0x065c9d…c394
4 touches
1 conflict
0x80aeeaf4…d5f5
0x065c9d…c394
3 touches
1 conflict
0x84a6c76b…ad16
0x065c9d…c394
3 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x390bbc42…b59c
0x065c9d…c394
2 touches
0 conflicts
0x8fc1e77a…a9a0
0x065c9d…c394
2 touches
0 conflicts
0x95593711…f20b
0x065c9d…c394
2 touches
0 conflicts
0xa2020d5b…9c78
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 0x3cbb6794aa…03ff13
Audit this contract →
← previous block·next block →recent activity