← previous blocknext block →recent activity
Analyzing
Block #76,438,054
22 transactions · 16 stateful · 2026-05-23 08:07:30 UTC
Parallelism
86/100
Blocked
31%
Avg conflicts / tx
0.32
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #76,438,054 · 22 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
2w03w16w07w18w210w011w012w113w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
6 touches
3 conflicts
0x25de453d…9573
0x34b655…2a6f
4 touches
1 conflict
0x65370db7…73b0
0x34b655…2a6f
4 touches
1 conflict
0xcb2dc2cb…a9e9
0x34b655…2a6f
4 touches
1 conflict
0xe63e4686…4596
0x34b655…2a6f
4 touches
1 conflict
0xb374d549…5e5e
0x754704…b603
4 touches
1 conflict
0x0335ae80…8414
0x8d66a4…3095
4 touches
1 conflict
0x17cd1479…00bb
0x8d66a4…3095
4 touches
1 conflict
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
3 conflicts on slot 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity