pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,483,070
← previous block
next block →
recent activity
Analyzing
Block #94,483,070
12 transactions · 11 stateful · 2026-08-09 11:57:27 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
#94,483,070
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5acec890
#2
updateDataFeedsValuesPartial
#3
execOrders
#4
execOrders
#5
execFwdPositionOps
· blocks 1
#7
execFwdPositionOps
#8
0x6a786b9f
#9
setData
#10
execOrders
#11
0xc7e3ec2c
#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
0xc824469a…6426
0x34b655…2a6f
4 touches
1 conflict
0x4c7c8c7f…d6fa
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x3368520b…ad9f
0x34b655…2a6f
2 touches
0 conflicts
0x3ab86b5a…8290
0x34b655…2a6f
2 touches
0 conflicts
0x5e800a72…0189
0x34b655…2a6f
2 touches
0 conflicts
0x6e2b56d3…be86
0x34b655…2a6f
2 touches
0 conflicts
0x6fb92ed4…7205
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
0xc824469a90…af6426
Audit this contract →
← previous block
·
next block →
recent activity