← previous blocknext block →recent activity
Analyzing
Block #72,431,305
8 transactions · 8 stateful · 2026-05-04 18:35:47 UTC
Parallelism
75/100
Blocked
13%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #72,431,305 · 8 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w05w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x0f48369b…3701
0x065c9d…c394
2 touches
0 conflicts
0x2019b6e0…f16e
0x065c9d…c394
2 touches
0 conflicts
0x5511ccfc…3b8d
0x065c9d…c394
2 touches
0 conflicts
0x7c083258…4533
0x065c9d…c394
2 touches
0 conflicts
0x9fc98f30…1f62
0x065c9d…c394
2 touches
0 conflicts
0xb96a4937…d4b5
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
1 conflict on slot 0xf2f76ab392…f3623e
Audit this contract →
← previous block·next block →recent activity