pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,837,894
← previous block
next block →
recent activity
Analyzing
Block #90,837,894
12 transactions · 11 stateful · 2026-07-27 18:01:30 UTC
Parallelism
83
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,837,894
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
0xab083028
#3
0x5a5d9a99
#4
updateDataFeedsValuesPartial
#5
execFwdPositionOps
· blocks 1
#7
0x57368ddf
#8
execFwdPositionOps
#9
transfer
#10
setData
#11
execOrders
#6
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe2e52e46…0894
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xbc5fc032…8d7d
0x34b655…2a6f
4 touches
1 conflict
0xbc5fc032…8d7e
0x34b655…2a6f
4 touches
1 conflict
0xc73549e8…2001
0x34b655…2a6f
4 touches
1 conflict
0x4ed586fd…c195
0x34b655…2a6f
3 touches
1 conflict
0xd9d0b0b5…32f5
0x34b655…2a6f
3 touches
1 conflict
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
0xe2e52e4663…6f0894
Audit this contract →
← previous block
·
next block →
recent activity