← previous blocknext block →recent activity
Analyzing
Block #76,223,052
16 transactions · 13 stateful · 2026-05-22 08:15:48 UTC
Parallelism
56/100
Blocked
46%
Avg conflicts / tx
0.88
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #76,223,052 · 16 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w111w212w313w414w515w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x388e001a…7e04
0x34b655…2a6f
8 touches
6 conflicts
0x874f5c70…608f
0x34b655…2a6f
6 touches
3 conflicts
0xc009105d…96f7
0x8d66a4…3095
4 touches
1 conflict
0xedb848fe…6534
0x34b655…2a6f
4 touches
1 conflict
0xf853eb8e…4027
0x34b655…2a6f
4 touches
1 conflict
0x50e10826…843b
0x8d66a4…3095
4 touches
1 conflict
0x8a35acfb…d1a7
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
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity