pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#75,335,049
← previous block
next block →
recent activity
Analyzing
Block #75,335,049
6 transactions · 5 stateful · 2026-05-18 05:26:37 UTC
Parallelism
67
/100
Blocked
20
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,335,049
· 6 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
0x6a0aa384
#3
setData
#4
0x39435dac
· blocks 1
#5
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7cee1be1…e770
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x30c10c87…22ec
0x34b655…2a6f
2 touches
0 conflicts
0x37d49489…9309
0x34b655…2a6f
2 touches
0 conflicts
0x5655f5c3…6b75
0x34b655…2a6f
2 touches
0 conflicts
0x676f9f01…a8ac
0x34b655…2a6f
2 touches
0 conflicts
0x81ceb686…4df3
0x34b655…2a6f
2 touches
0 conflicts
0x85a88798…f85e
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
1 conflict on slot
0x7cee1be1f4…b4e770
Audit this contract →
← previous block
·
next block →
recent activity