← previous blocknext block →recent activity
Analyzing
Block #76,226,681
16 transactions · 14 stateful · 2026-05-22 08:40:11 UTC
Parallelism
50/100
Blocked
64%
Avg conflicts / tx
1.44
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #76,226,681 · 16 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w16w07w18w29w310w413w514w615w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xea57afd0…4232
0x34b655…2a6f
10 touches
10 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
10 touches
10 conflicts
0xea02471d…1542
0x34b655…2a6f
10 touches
10 conflicts
0xb95863bf…6d4c
0x34b655…2a6f
8 touches
6 conflicts
0x9c3004b2…5421
0x34b655…2a6f
8 touches
6 conflicts
0x085df2c1…305a
0x34b655…2a6f
8 touches
6 conflicts
0x95de2003…c7de
0x34b655…2a6f
8 touches
6 conflicts
0xdc54eb34…fe58
0x34b655…2a6f
6 touches
3 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
10 conflicts on slot 0xea57afd097…7f4232
Audit this contract →
← previous block·next block →recent activity