pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #75,079,746
23 transactions · 17 stateful · 2026-05-17 01:00:31 UTC
Parallelism
83/100
Blocked
53%
Avg conflicts / tx
0.48
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #75,079,746 · 23 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
2w03w14w06w07w08w110w111w115w217w318w320w221w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x631b4113…baa9
0x34b655…2a6f
6 touches
3 conflicts
0x43552446…d185
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0018
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0028
0x1b6862…e19c
4 touches
1 conflict
0x261261a7…616e
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
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: 0x34b6552d…112a6f
3 conflicts on slot 0x631b41138f…31baa9
Audit this contract →
← previous block·next block →recent activity