← previous blocknext block →recent activity
Analyzing
Block #76,507,292
10 transactions · 7 stateful · 2026-05-23 15:48:30 UTC
Parallelism
80/100
Blocked
29%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #76,507,292 · 10 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w07w19w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb6b74ae0…8d5e
0xea1b8e…c5ec
4 touches
1 conflict
0x25b00bf5…3e2e
0xea1b8e…c5ec
4 touches
1 conflict
0x00bac013…a28c
0x91b81b…6d56
4 touches
1 conflict
0x60f7fbaf…bd58
0x34b655…2a6f
4 touches
1 conflict
0x5b645d44…28c2
0x1efe02…37d6
2 touches
0 conflicts
0x8ffee6b0…a201
0x1efe02…37d6
2 touches
0 conflicts
0xf853eb8e…401e
0x34b655…2a6f
2 touches
0 conflicts
0x9560013d…8caf
0x91b81b…6d56
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: LeverUp: LeverUp
1 conflict on slot 0xb6b74ae0ff…d48d5e
Audit this contract →
← previous block·next block →recent activity