pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,338,598
← previous block
next block →
recent activity
Analyzing
Block #93,338,598
10 transactions · 9 stateful · 2026-08-05 11:46:07 UTC
Parallelism
70
/100
Blocked
33
%
Avg conflicts / tx
0.4
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,338,598
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x6bdec372
#2
0x5acec890
· blocks 2
#5
updateDataFeedsValuesPartial
#6
execFwdPositionOps
· blocks 1
#8
0x6a7322f7
#9
setData
#3
0x5acec890
· blocks 1
#7
execFwdPositionOps
#4
0x5acec890
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
4
w2
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x2c539d94…b63a
0x34b655…2a6f
4 touches
1 conflict
0xa0c9bb84…ba20
0x34b655…2a6f
4 touches
1 conflict
0x26f8ccf5…90bd
0x34b655…2a6f
2 touches
0 conflicts
0x496e3020…0c46
0x34b655…2a6f
2 touches
0 conflicts
0x8e485ef0…8a8a
0x3bd359…433a
2 touches
0 conflicts
0xebc2e0d7…958e
0x3bd359…433a
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
3 conflicts on slot
0xca841faae5…71486a
Audit this contract →
← previous block
·
next block →
recent activity