pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,250,536
← previous block
next block →
recent activity
Analyzing
Block #94,250,536
11 transactions · 11 stateful · 2026-08-08 16:17:19 UTC
Parallelism
82
/100
Blocked
18
%
Avg conflicts / tx
0.27
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,250,536
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
execOrders
· blocks 1
#4
updatePrices
#5
0x5acec890
· blocks 1
#6
0x5acec890
#7
execFwdPositionOps
· blocks 1
#9
forward
#10
setData
#3
execOrders
#8
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
5
w0
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x742436a7…c4d4
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4f1ad4b4…e00a
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x75f928fc…0465
0x34b655…2a6f
2 touches
0 conflicts
0x81da6711…3869
0x34b655…2a6f
2 touches
0 conflicts
0x87292c3e…5e25
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
0x742436a7e5…69c4d4
Audit this contract →
← previous block
·
next block →
recent activity