pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#91,424,416
← previous block
next block →
recent activity
Analyzing
Block #91,424,416
11 transactions · 10 stateful · 2026-07-29 19:14:43 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#91,424,416
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
executeBatch
· blocks 1
#3
0xed82b078
#4
execFwdPositionOps
#5
updateDataFeedsValuesPartial
#6
0x6a6a519b
#7
transfer
#8
setData
#9
0x59558d29
#10
0xc7e3ec2c
#2
executeBatch
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
0x82941720…6fde
0xe52b14…7230
4 touches
1 conflict
0x32363a87…c2cc
0xe52b14…7230
4 touches
1 conflict
0x32363a87…c2ce
0xe52b14…7230
4 touches
1 conflict
0x82941720…6fdc
0xe52b14…7230
4 touches
1 conflict
0xf79df061…e005
0xe52b14…7230
4 touches
1 conflict
0x3ec27d59…38d8
0xe52b14…7230
2 touches
1 conflict
0x58733c38…f2cd
0xe52b14…7230
2 touches
0 conflicts
0x09000000…0001
0x000000…1000
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:
0xe52b1424…bb7230
1 conflict on slot
0x82941720fd…e36fde
Audit this contract →
← previous block
·
next block →
recent activity