← previous blocknext block →recent activity
Analyzing
Block #73,751,352
28 transactions · 21 stateful · 2026-05-10 21:15:02 UTC
Parallelism
86/100
Blocked
48%
Avg conflicts / tx
0.68
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #73,751,352 · 28 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
2w04w05w06w17w29w011w112w213w314w117w018w119w220w323w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xab3526…fa38
8 touches
6 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
8 touches
6 conflicts
0x17606ba6…1b6e
0x754704…b603
6 touches
3 conflicts
0x6d356c16…9830
0xd32edf…ff58
5 touches
3 conflicts
0x0eac6378…36f4
0x34b655…2a6f
4 touches
1 conflict
0x150af51d…9c42
0x34b655…2a6f
4 touches
1 conflict
0x4997d347…5ebe
0x34b655…2a6f
4 touches
1 conflict
0x7537eda8…9070
0x34b655…2a6f
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: 0xab35264b…1cfa38
6 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity