pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,540,526
← previous block
next block →
recent activity
Analyzing
Block #93,540,526
11 transactions · 10 stateful · 2026-08-06 04:41:18 UTC
Parallelism
82
/100
Blocked
20
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,540,526
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrder
· blocks 2
#2
0xeb282f7f
#3
0x5acec890
#4
updateDataFeedsValuesPartial
#6
execFwdPositionOps
#8
0x3f5c179b
#9
forward
#10
setData
#5
execFwdPositionOps
#7
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
5
w1
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb6fcbbb7…2b31
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x706c758c…2fdb
0x34b655…2a6f
4 touches
1 conflict
0xb56b94f6…a7f1
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
2 touches
0 conflicts
0x948836ff…59ab
0x34b655…2a6f
2 touches
0 conflicts
0xc824469a…6426
0x34b655…2a6f
2 touches
0 conflicts
0xd03f3825…8b17
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
0xb6fcbbb7f3…142b31
Audit this contract →
← previous block
·
next block →
recent activity