pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,182,119
← previous block
next block →
recent activity
Analyzing
Block #93,182,119
7 transactions · 6 stateful · 2026-08-04 22:39:24 UTC
Parallelism
71
/100
Blocked
17
%
Avg conflicts / tx
0.14
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,182,119
· 7 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
execFwdPositionOps
· blocks 1
#3
setData
#5
updateDataFeedsValuesPartial
#6
0x59558d29
#4
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x939cdd56…00c8
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x188ce86d…8bec
0x34b655…2a6f
2 touches
0 conflicts
0x18fe7fdc…77f7
0x34b655…2a6f
2 touches
0 conflicts
0x33f54bd6…9ac3
0x34b655…2a6f
2 touches
0 conflicts
0x3661f59a…874a
0x34b655…2a6f
2 touches
0 conflicts
0x3d26ad42…d70c
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
0x939cdd567e…a300c8
Audit this contract →
← previous block
·
next block →
recent activity