pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,301,981
← previous block
next block →
recent activity
Analyzing
Block #93,301,981
11 transactions · 9 stateful · 2026-08-05 08:42:01 UTC
Parallelism
82
/100
Blocked
11
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,301,981
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
0xee83e0a5
#3
forward
#4
execFwdPositionOps
· blocks 1
#5
execFwdPositionOps
#7
transfer
#8
setData
#9
0x59558d29
#10
0xc7e3ec2c
#6
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x5311f864…0984
0x754704…b603
2 touches
0 conflicts
0x04142098…85b9
0x928dc8…8207
2 touches
0 conflicts
0x4a54898d…4b7c
0x928dc8…8207
2 touches
0 conflicts
0x540ec0fe…7524
0x928dc8…8207
2 touches
0 conflicts
0x5c5c5b67…726b
0x928dc8…8207
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
0xc824469a90…af6425
Audit this contract →
← previous block
·
next block →
recent activity