← previous blocknext block →recent activity
Analyzing
Block #73,743,865
10 transactions · 10 stateful · 2026-05-10 20:24:30 UTC
Parallelism
60/100
Blocked
30%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #73,743,865 · 10 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
2w05w16w27w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x0ac31945…2c72
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x529acb6a…fcc6
0x065c9d…c394
2 touches
0 conflicts
0x96d80d99…6b63
0x065c9d…c394
2 touches
0 conflicts
0x438cf5f6…f077
0x2a68ba…90c5
2 touches
0 conflicts
0x968bdacb…f461
0x2a68ba…90c5
2 touches
0 conflicts
0x09106a95…1467
0x33176b…e078
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
3 conflicts on slot 0xf2f76ab392…f3623e
Audit this contract →
← previous block·next block →recent activity