pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#75,681,966
← previous block
next block →
recent activity
Analyzing
Block #75,681,966
12 transactions · 9 stateful · 2026-05-19 20:11:05 UTC
Parallelism
83
/100
Blocked
11
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,681,966
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
execute
#3
0xab083028
#4
0x0f6795d9
#5
0x0f6795d9
#6
forward
#7
updateDataFeedsValuesPartial
#8
0xe9316489
· blocks 1
#10
setData
#11
0x42dd8743
#9
0xe9316489
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x581b5c2f…ee54
0x96b79e…d00a
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x0a7eaf36…083e
0x065c9d…c394
2 touches
0 conflicts
0x22c04c9c…53aa
0x065c9d…c394
2 touches
0 conflicts
0x443d196a…3ce1
0x065c9d…c394
2 touches
0 conflicts
0x63751385…326d
0x065c9d…c394
2 touches
0 conflicts
0x06e40499…165e
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:
0x96b79ef4…d2d00a
1 conflict on slot
0x581b5c2fd6…56ee54
Audit this contract →
← previous block
·
next block →
recent activity