← previous blocknext block →recent activity
Analyzing
Block #73,751,136
10 transactions · 9 stateful · 2026-05-10 21:13:35 UTC
Parallelism
80/100
Blocked
22%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #73,751,136 · 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
2w03w16w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x4d87512b…897c
0x065c9d…c394
4 touches
1 conflict
0x2b0191f0…f60c
0xd32edf…ff58
3 touches
1 conflict
0x2bab21b3…5a73
0x065c9d…c394
2 touches
0 conflicts
0x2d01b4f1…ae8c
0x065c9d…c394
2 touches
0 conflicts
0x59560728…da87
0x065c9d…c394
2 touches
0 conflicts
0x6d7e03ad…fb39
0x065c9d…c394
2 touches
0 conflicts
0xa761ef0f…9f21
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