← previous blocknext block →recent activity
Analyzing
Block #72,972,434
14 transactions · 13 stateful · 2026-05-07 06:41:01 UTC
Parallelism
64/100
Blocked
31%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #72,972,434 · 14 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w38w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x70b2f813…783c
0x2a68ba…90c5
6 touches
3 conflicts
0x54468cc2…2e9e
0xd32edf…ff58
5 touches
3 conflicts
0x24118d33…c9ef
0x065c9d…c394
5 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x8d47c9a4…f120
0x1b6862…e19c
4 touches
1 conflict
0xce7bfe5e…5e58
0x065c9d…c394
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
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 0x70b2f81398…04783c
Audit this contract →
← previous block·next block →recent activity