← previous blocknext block →recent activity
Analyzing
Block #73,494,937
11 transactions · 10 stateful · 2026-05-09 16:37:39 UTC
Parallelism
64/100
Blocked
30%
Avg conflicts / tx
0.55
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #73,494,937 · 11 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w27w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x4d87512b…897c
0x065c9d…c394
4 touches
1 conflict
0x039c21df…86fe
0x065c9d…c394
2 touches
0 conflicts
0x48882edd…1d83
0x065c9d…c394
2 touches
0 conflicts
0x4d425a58…4268
0x065c9d…c394
2 touches
0 conflicts
0x9b36b3e0…1502
0x065c9d…c394
2 touches
0 conflicts
0x9d8f1a0e…edd7
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: MarginAccount
6 conflicts on slot 0xf2f76ab392…f3623e
Audit this contract →
← previous block·next block →recent activity