← previous blocknext block →recent activity
Analyzing
Block #76,225,259
10 transactions · 8 stateful · 2026-05-22 08:30:42 UTC
Parallelism
70/100
Blocked
25%
Avg conflicts / tx
0.3
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #76,225,259 · 10 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x532023a5…d800
0xe52b14…7230
6 touches
3 conflicts
0xd58b5c38…3b7c
0x754704…b603
6 touches
3 conflicts
0x0b0c2e8d…c1b8
0xe52b14…7230
6 touches
3 conflicts
0x5149ba0e…d954
0x754704…b603
6 touches
3 conflicts
0x8ffa3328…ce11
0xe52b14…7230
6 touches
3 conflicts
0xf79df061…e005
0xe52b14…7230
6 touches
3 conflicts
0x9d3c6179…11fa
0xe52b14…7230
3 touches
1 conflict
0x14ba0e5f…a749
0x188d58…ea8e
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: 0xe52b1424…bb7230
3 conflicts on slot 0x532023a546…d6d800
Audit this contract →
← previous block·next block →recent activity