← previous blocknext block →recent activity
Analyzing
Block #74,901,233
7 transactions · 6 stateful · 2026-05-16 05:07:35 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,901,233 · 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
1w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfda08232…96e7
0x065c9d…c394
4 touches
1 conflict
0x2de649b5…fd0b
0x065c9d…c394
3 touches
1 conflict
0xc996b12c…2d4f
0x065c9d…c394
3 touches
1 conflict
0x853e0c3a…92dd
0x065c9d…c394
2 touches
0 conflicts
0xa0163276…946d
0x065c9d…c394
2 touches
0 conflicts
0xb4e446fd…34ca
0x065c9d…c394
2 touches
0 conflicts
0x30276c1c…47b4
0x2a68ba…90c5
2 touches
0 conflicts
0x765c236f…ff45
0x2a68ba…90c5
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 0xfda08232fd…db96e7
Audit this contract →
← previous block·next block →recent activity