pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,475,556
← previous block
next block →
recent activity
Analyzing
Block #94,475,556
10 transactions · 9 stateful · 2026-08-09 11:19:39 UTC
Parallelism
60
/100
Blocked
33
%
Avg conflicts / tx
0.3
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,475,556
· 10 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
0xab083028
#2
0x5acec890
· blocks 1
#4
updateDataFeedsValuesPartial
#6
execOrders
#8
transfer
#9
setData
#3
execFwdPositionOps
· blocks 1
#5
execFwdPositionOps
· blocks 1
#7
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
5
w2
7
w3
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe58009e8…fe3f
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6426
0x34b655…2a6f
4 touches
1 conflict
0xcffc17bc…3544
0x34b655…2a6f
4 touches
1 conflict
0xd22ea5b1…7dcb
0x34b655…2a6f
4 touches
1 conflict
0x176afbb9…78da
0x34b655…2a6f
4 touches
1 conflict
0x3230413b…bc7f
0x34b655…2a6f
4 touches
1 conflict
0x5e32f9d6…43bc
0x34b655…2a6f
4 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
0xe58009e820…f6fe3f
Audit this contract →
← previous block
·
next block →
recent activity