pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#83,484,609
← previous block
next block →
recent activity
Analyzing
Block #83,484,609
9 transactions · 8 stateful · 2026-06-24 23:36:17 UTC
Parallelism
67
/100
Blocked
25
%
Avg conflicts / tx
0.44
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#83,484,609
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x98c6107a
#2
0x98717539
· blocks 1
#3
updateDataFeedsValuesPartial
#4
setData
#5
execFwdPositionOps
#6
execFwdPositionOps
· blocks 2
#7
execOrders
· blocks 1
#8
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
6
w0
7
w1
8
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xfefb0189…f726
0x34b655…2a6f
4 touches
1 conflict
0x9e878bcd…f4b5
0x34b655…2a6f
4 touches
1 conflict
0x61edf7f9…956d
0x34b655…2a6f
2 touches
0 conflicts
0x62554ce4…109e
0x34b655…2a6f
2 touches
0 conflicts
0xc824469a…6425
0x34b655…2a6f
2 touches
0 conflicts
0x12a9b76e…cb76
0x3bd359…433a
2 touches
0 conflicts
0x44ed742f…63f5
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
0xd98b3c102b…ca67b8
Audit this contract →
← previous block
·
next block →
recent activity