← previous blocknext block →recent activity
Analyzing
Block #73,270,294
18 transactions · 15 stateful · 2026-05-08 15:42:56 UTC
Parallelism
78/100
Blocked
47%
Avg conflicts / tx
0.72
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #73,270,294 · 18 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
1w02w03w14w25w310w111w213w315w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
8 touches
6 conflicts
0x0b390c61…dc07
0x065c9d…c394
8 touches
6 conflicts
0x0d622e34…0000
0x681e90…ae09
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xd3388761…cf45
0x065c9d…c394
3 touches
1 conflict
0x8ab8b801…6420
0x065c9d…c394
3 touches
1 conflict
0xbdff944d…447e
0x2a68ba…90c5
2 touches
0 conflicts
0x01a89030…f786
0x368ee5…7ca4
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
6 conflicts on slot 0xf2f76ab392…f3623e
Audit this contract →
← previous block·next block →recent activity