← previous blocknext block →recent activity
Analyzing
Block #73,375,632
9 transactions · 9 stateful · 2026-05-09 03:23:44 UTC
Parallelism
56/100
Blocked
33%
Avg conflicts / tx
0.44
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #73,375,632 · 9 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
1w02w13w24w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe038916c…b1be
0x2a68ba…90c5
6 touches
3 conflicts
0x5d82c9b5…004c
0x3bd359…433a
4 touches
1 conflict
0x4039b31f…0f4a
0x754704…b603
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0xc0c1dea0…1a32
0x5afd3e…7620
4 touches
1 conflict
0x00000000…0005
0x5afd3e…7620
4 touches
1 conflict
0x00000000…0004
0x5afd3e…7620
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
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
3 conflicts on slot 0xe038916c87…fab1be
Audit this contract →
← previous block·next block →recent activity