pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,061,838
← previous block
next block →
recent activity
Analyzing
Block #94,061,838
8 transactions · 6 stateful · 2026-08-08 00:22:53 UTC
Parallelism
75
/100
Blocked
17
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,061,838
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
0x5acec890
· blocks 1
#4
execFwdPositionOps
#5
updateDataFeedsValuesPartial
#6
0xed82b078
#7
setData
#3
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcf005309…1129
0x34b655…2a6f
4 touches
1 conflict
0xeb0b1d43…9559
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x283cc018…cce0
0x34b655…2a6f
2 touches
0 conflicts
0x31644e15…5b87
0x34b655…2a6f
2 touches
0 conflicts
0x58722c60…a81a
0x34b655…2a6f
2 touches
0 conflicts
0x5a1463b5…309f
0x34b655…2a6f
2 touches
0 conflicts
0x6e6a8155…9636
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
0xcf005309a1…901129
Audit this contract →
← previous block
·
next block →
recent activity