← previous blocknext block →recent activity
Analyzing
Block #73,029,412
19 transactions · 15 stateful · 2026-05-07 13:00:15 UTC
Parallelism
79/100
Blocked
20%
Avg conflicts / tx
0.32
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #73,029,412 · 19 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
2w09w110w211w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x0b390c61…dc07
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xbcb2001e…2a04
0x065c9d…c394
4 touches
1 conflict
0xd590c7d5…fe76
0x065c9d…c394
3 touches
1 conflict
0x697e8fd8…a688
0x065c9d…c394
2 touches
0 conflicts
0x805186e3…c11d
0x065c9d…c394
2 touches
0 conflicts
0x8ad4b4e7…efe4
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 0xf2f76ab392…f3623e
Audit this contract →
← previous block·next block →recent activity