← previous blocknext block →recent activity
Analyzing
Block #76,229,625
9 transactions · 7 stateful · 2026-05-22 08:59:48 UTC
Parallelism
56/100
Blocked
43%
Avg conflicts / tx
0.44
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #76,229,625 · 9 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w28w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
6 touches
3 conflicts
0xa009aa7b…a5ba
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x0335ae80…8414
0x8d66a4…3095
4 touches
1 conflict
0x17cd1479…00bb
0x8d66a4…3095
4 touches
1 conflict
0x8a35acfb…d1a8
0x8d66a4…3095
4 touches
1 conflict
0x8a35acfb…d1a9
0x8d66a4…3095
4 touches
1 conflict
0x9d1bb389…c7d9
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