← previous blocknext block →recent activity
Analyzing
Block #73,035,856
32 transactions · 21 stateful · 2026-05-07 13:43:10 UTC
Parallelism
84/100
Blocked
52%
Avg conflicts / tx
0.66
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #73,035,856 · 32 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
2w04w05w17w28w310w418w019w122w024w125w126w227w330w231w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xd574ca…7ab1
10 touches
10 conflicts
0xdaca243a…f9de
0x34b655…2a6f
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x0b390c61…dc07
0x065c9d…c394
6 touches
3 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
4 touches
1 conflict
0x4674d7b8…edef
0x065c9d…c394
4 touches
1 conflict
0xb8eb16b2…d38b
0x065c9d…c394
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: 0xd574cae5…037ab1
10 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity