← previous blocknext block →recent activity
Analyzing
Block #76,091,140
17 transactions · 15 stateful · 2026-05-21 17:37:20 UTC
Parallelism
76/100
Blocked
40%
Avg conflicts / tx
0.53
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #76,091,140 · 17 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
1w02w15w06w27w111w012w113w214w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x42bb0ac5…6b33
0x34b655…2a6f
4 touches
1 conflict
0x8c49c85c…ee96
0x34b655…2a6f
4 touches
1 conflict
0xcc71b2e1…d463
0xa6afd3…d132
3 touches
1 conflict
0x4c6b2355…2cc7
0xd32edf…ff58
3 touches
1 conflict
0xdb067026…9eb8
0x1d1325…2305
2 touches
0 conflicts
0xe2263bea…6a9f
0x1d1325…2305
2 touches
0 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
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity