← previous blocknext block →recent activity
Analyzing
Block #74,764,813
14 transactions · 12 stateful · 2026-05-15 13:57:15 UTC
Parallelism
79/100
Blocked
42%
Avg conflicts / tx
0.43
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #74,764,813 · 14 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
1w02w13w04w15w06w17w29w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x00000000…0002
0xab3526…fa38
4 touches
1 conflict
0x3a24677e…4ea9
0xd32edf…ff58
3 touches
1 conflict
0x10f5f4d8…572e
0x34b655…2a6f
2 touches
0 conflicts
0x150af51d…9c42
0x34b655…2a6f
2 touches
0 conflicts
0x1674d3d4…275f
0x34b655…2a6f
2 touches
0 conflicts
0x3862f09d…5f8e
0x34b655…2a6f
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
3 conflicts on slot 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity