← previous blocknext block →recent activity
Analyzing
Block #74,938,024
10 transactions · 9 stateful · 2026-05-16 09:13:01 UTC
Parallelism
80/100
Blocked
22%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,938,024 · 10 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
2w07w18w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x65d3f27b…83b5
0x065c9d…c394
4 touches
1 conflict
0x76f22e57…8a59
0x065c9d…c394
3 touches
1 conflict
0x8e3117c8…e6f6
0x065c9d…c394
3 touches
1 conflict
0xb002a499…cf0a
0x065c9d…c394
3 touches
1 conflict
0x31b35a0a…88f9
0x065c9d…c394
3 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…001d
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…002d
0x1b6862…e19c
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 0x65d3f27bec…5183b5
Audit this contract →
← previous block·next block →recent activity