← previous blocknext block →recent activity
Analyzing
Block #76,225,226
10 transactions · 7 stateful · 2026-05-22 08:30:28 UTC
Parallelism
80/100
Blocked
14%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #76,225,226 · 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
4w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf9b8ae99…32b4
0x34b655…2a6f
4 touches
1 conflict
0xf9b8ae99…32b3
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x002aebc8…0646
0x754704…b603
2 touches
0 conflicts
0x06956408…967b
0x754704…b603
2 touches
0 conflicts
0x57991e16…4aa2
0x754704…b603
2 touches
0 conflicts
0xfd4bd0e6…5918
0x754704…b603
2 touches
0 conflicts
0x4aa3dc54…b2b0
0xae0830…85fe
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: Perpl
1 conflict on slot 0xf9b8ae99dc…3532b4
Audit this contract →
← previous block·next block →recent activity