pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#91,977,395
← previous block
next block →
recent activity
Analyzing
Block #91,977,395
8 transactions · 8 stateful · 2026-07-31 17:37:14 UTC
Parallelism
75
/100
Blocked
13
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#91,977,395
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0f6795d9
· blocks 1
#3
0x39435dac
#4
updateDataFeedsValuesPartial
#5
0x6a6cddc2
#6
setData
#7
0x59558d29
#2
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x31b39922…1e65
0x34b655…2a6f
4 touches
1 conflict
0x31b39922…1e66
0x34b655…2a6f
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
2 touches
0 conflicts
0x054afe69…16e8
0x34b655…2a6f
2 touches
0 conflicts
0x068934bf…4f42
0x34b655…2a6f
2 touches
0 conflicts
0x09df480a…c40e
0x34b655…2a6f
2 touches
0 conflicts
0x1205ebd6…dad6
0x34b655…2a6f
2 touches
0 conflicts
0x1bb624f3…c1b3
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
0x31b3992285…921e65
Audit this contract →
← previous block
·
next block →
recent activity