← previous blocknext block →recent activity
Analyzing
Block #73,989,917
13 transactions · 9 stateful · 2026-05-11 23:49:27 UTC
Parallelism
77/100
Blocked
44%
Avg conflicts / tx
0.46
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #73,989,917 · 13 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w18w29w010w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x046a928e…0012
0x2a68ba…90c5
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x6f08361d…bda6
0x065c9d…c394
4 touches
1 conflict
0xf537eaa0…73c8
0x065c9d…c394
4 touches
1 conflict
0x1f460dee…0e90
0x065c9d…c394
2 touches
0 conflicts
0x27182caf…83b9
0x065c9d…c394
2 touches
0 conflicts
0xb254a588…1201
0x065c9d…c394
2 touches
0 conflicts
0xe113a736…6923
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
3 conflicts on slot 0x046a928e85…e50012
Audit this contract →
← previous block·next block →recent activity