← previous blocknext block →recent activity
Analyzing
Block #73,417,829
10 transactions · 10 stateful · 2026-05-09 08:04:40 UTC
Parallelism
60/100
Blocked
50%
Avg conflicts / tx
0.9
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #73,417,829 · 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
1w03w14w25w36w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x6779f99f…0884
0x065c9d…c394
4 touches
1 conflict
0x24ef0c1d…e3fd
0x065c9d…c394
4 touches
1 conflict
0x325507cf…e155
0x065c9d…c394
4 touches
1 conflict
0x9c97dfc6…9bb9
0x065c9d…c394
4 touches
1 conflict
0xe20db839…7577
0x065c9d…c394
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x25cebccd…85ed
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