← previous blocknext block →recent activity
Analyzing
Block #74,266,802
13 transactions · 12 stateful · 2026-05-13 06:32:29 UTC
Parallelism
85/100
Blocked
17%
Avg conflicts / tx
0.15
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,266,802 · 13 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
1w04w17w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcf3283ba…c9fa
0x065c9d…c394
4 touches
1 conflict
0x3e382434…1b8e
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xaf8b0823…f7a6
0x065c9d…c394
4 touches
1 conflict
0x5b0479b0…8f36
0x065c9d…c394
3 touches
1 conflict
0xcb35757a…f968
0x065c9d…c394
3 touches
1 conflict
0x7d9ee7c6…f8b8
0x065c9d…c394
2 touches
0 conflicts
0xa1bc12f8…f2dd
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 0xcf3283bab2…c3c9fa
Audit this contract →
← previous block·next block →recent activity