pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#91,971,706
← previous block
next block →
recent activity
Analyzing
Block #91,971,706
9 transactions · 9 stateful · 2026-07-31 17:08:37 UTC
Parallelism
78
/100
Blocked
22
%
Avg conflicts / tx
0.22
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#91,971,706
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
executeBatch
#2
0x3f5c179b
#3
execFwdPositionOps
· blocks 2
#5
0x94defb17
#7
setData
#8
0x59558d29
#4
execFwdPositionOps
#6
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8765edd1…a7d5
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xa4e9800f…4ab1
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x0a3c16de…77eb
0xe52b14…7230
2 touches
0 conflicts
0x17bbe4f8…08c5
0xe52b14…7230
2 touches
0 conflicts
0x32363a87…c2cc
0xe52b14…7230
2 touches
0 conflicts
0x3cebc8f1…975c
0xe52b14…7230
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
0x8765edd17a…a5a7d5
Audit this contract →
← previous block
·
next block →
recent activity