← previous blocknext block →recent activity
Analyzing
Block #76,243,186
13 transactions · 9 stateful · 2026-05-22 10:30:07 UTC
Parallelism
85/100
Blocked
22%
Avg conflicts / tx
0.15
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #76,243,186 · 13 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
5w06w112w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x69f45285…9e9d
0x34b655…2a6f
4 touches
1 conflict
0x60f7fbaf…bd58
0x34b655…2a6f
4 touches
1 conflict
0x5648d337…a780
0x34b655…2a6f
4 touches
1 conflict
0x729c91b8…9537
0x188d58…ea8e
2 touches
0 conflicts
0x729c91b8…9538
0x188d58…ea8e
2 touches
0 conflicts
0x696a27c8…5847
0x2a68ba…90c5
2 touches
0 conflicts
0x178fe051…465a
0x34b655…2a6f
2 touches
0 conflicts
0x5fb643e5…d442
0x34b655…2a6f
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 0x69f4528550…979e9d
Audit this contract →
← previous block·next block →recent activity