← previous blocknext block →recent activity
Analyzing
Block #73,967,501
25 transactions · 18 stateful · 2026-05-11 21:18:53 UTC
Parallelism
76/100
Blocked
56%
Avg conflicts / tx
0.68
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #73,967,501 · 25 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w18w311w012w114w217w018w120w321w422w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
8 touches
6 conflicts
0x0d0b2509…074d
0x3bd359…433a
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0xe6455d1f…1029
0x754704…b603
6 touches
3 conflicts
0x485d2778…aa5c
0x1b6862…e19c
6 touches
3 conflicts
0x41e28e83…2846
0xd32edf…ff58
5 touches
3 conflicts
0x6f08361d…bda6
0x065c9d…c394
4 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
6 conflicts on slot 0xf2f76ab392…f3623e
Audit this contract →
← previous block·next block →recent activity