← previous blocknext block →recent activity
Analyzing
Block #74,460,243
12 transactions · 11 stateful · 2026-05-14 03:59:43 UTC
Parallelism
83/100
Blocked
9%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,460,243 · 12 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
0x5c8c6ab6…dc36
0x065c9d…c394
4 touches
1 conflict
0x999d60fe…4992
0x065c9d…c394
4 touches
1 conflict
0x131e8533…56b9
0x065c9d…c394
3 touches
1 conflict
0x1d76bb21…9636
0x065c9d…c394
3 touches
1 conflict
0x3054cee9…bbd4
0x065c9d…c394
2 touches
0 conflicts
0x47b807a2…3307
0x065c9d…c394
2 touches
0 conflicts
0x4dce3d2f…47db
0x065c9d…c394
2 touches
0 conflicts
0xdc85546c…9217
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 0x5c8c6ab6f0…86dc36
Audit this contract →
← previous block·next block →recent activity