← previous blocknext block →recent activity
Analyzing
Block #76,174,088
12 transactions · 11 stateful · 2026-05-22 02:49:51 UTC
Parallelism
67/100
Blocked
55%
Avg conflicts / tx
0.67
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #76,174,088 · 12 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
1w02w13w24w35w36w07w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x34f825d9…d14d
0x34b655…2a6f
6 touches
3 conflicts
0xf3d7a307…4d63
0x065c9d…c394
6 touches
3 conflicts
0x9fc6ea79…e2dc
0x34b655…2a6f
6 touches
3 conflicts
0x35b65947…44d1
0xc8689a…ee79
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x1b5d2e60…99b5
0x34b655…2a6f
4 touches
1 conflict
0x3c35979a…975d
0x34b655…2a6f
4 touches
1 conflict
0x4ede2893…29cb
0x34b655…2a6f
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 0x34f825d9f0…c4d14d
Audit this contract →
← previous block·next block →recent activity