← previous blocknext block →recent activity
Analyzing
Block #73,686,941
8 transactions · 8 stateful · 2026-05-10 14:00:26 UTC
Parallelism
50/100
Blocked
38%
Avg conflicts / tx
0.75
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #73,686,941 · 8 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
1w05w16w27w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x7bf6485f…2eae
0x065c9d…c394
4 touches
1 conflict
0x65b27097…ab7d
0x065c9d…c394
4 touches
1 conflict
0x195d3dca…a6a4
0x065c9d…c394
4 touches
1 conflict
0x9894e703…fb17
0x065c9d…c394
3 touches
1 conflict
0x700ae823…e486
0x065c9d…c394
3 touches
1 conflict
0xc9b52f7b…a259
0x065c9d…c394
3 touches
1 conflict
0xdab7fa55…2e76
0x065c9d…c394
3 touches
1 conflict
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