← previous blocknext block →recent activity
Analyzing
Block #74,022,867
8 transactions · 7 stateful · 2026-05-12 03:30:00 UTC
Parallelism
75/100
Blocked
14%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,022,867 · 8 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
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xaeea2be2…174c
0x065c9d…c394
3 touches
1 conflict
0x30276c1c…47b4
0x2a68ba…90c5
3 touches
1 conflict
0x125d97a3…89e2
0x065c9d…c394
2 touches
0 conflicts
0x2d106999…b6c6
0x065c9d…c394
2 touches
0 conflicts
0x782d0cdf…cff4
0x065c9d…c394
2 touches
0 conflicts
0xb72ac5b5…c0d8
0x065c9d…c394
2 touches
0 conflicts
0xc07dcbf8…2ece
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity