pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,373,177
← previous block
next block →
recent activity
Analyzing
Block #95,373,177
10 transactions · 9 stateful · 2026-08-12 14:48:50 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,373,177
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
0xab083028
#3
forward
#4
0x3f5c179b
· blocks 1
#6
simpleHarvest
#7
execFwdPositionOps
#8
updateDataFeedsValuesPartial
#9
setData
#5
batchUpdate
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
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x352c45ab…a8ee
0x851145…3f07
4 touches
1 conflict
0x413476a1…3e03
0x851145…3f07
4 touches
1 conflict
0xbb8dd99f…bb3f
0x851145…3f07
4 touches
1 conflict
0x982ba7f1…e834
0x11ed3b…2c96
2 touches
0 conflicts
0xa3f33f3e…804f
0x11ed3b…2c96
2 touches
0 conflicts
0xab2f6eed…254a
0x188d58…ea8e
2 touches
0 conflicts
0xab2f6eed…254b
0x188d58…ea8e
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:
0x851145ea…9f3f07
1 conflict on slot
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity