← previous blocknext block →recent activity
Analyzing
Block #74,759,784
24 transactions · 19 stateful · 2026-05-15 13:23:37 UTC
Parallelism
79/100
Blocked
47%
Avg conflicts / tx
0.58
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #74,759,784 · 24 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w08w09w110w213w014w115w217w118w020w121w322w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5cfec795…7c0e
0x34b655…2a6f
6 touches
3 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
6 touches
3 conflicts
0xd4cf6f15…bd4c
0xd32edf…ff58
5 touches
3 conflicts
0x7b97d40a…09ed
0x34b655…2a6f
4 touches
1 conflict
0x94710b77…a921
0x34b655…2a6f
4 touches
1 conflict
0xc5940545…27fe
0x34b655…2a6f
4 touches
1 conflict
0xcf17589f…048c
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
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 0x5cfec7957f…867c0e
Audit this contract →
← previous block·next block →recent activity