pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,201,053
← previous block
next block →
recent activity
Analyzing
Block #94,201,053
10 transactions · 8 stateful · 2026-08-08 12:06:23 UTC
Parallelism
70
/100
Blocked
25
%
Avg conflicts / tx
0.2
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,201,053
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
execOrders
#2
execOrders
#3
0x5acec890
· blocks 1
#5
updateDataFeedsValuesPartial
#6
execFwdPositionOps
#7
execFwdPositionOps
#8
setData
#4
0x5acec890
· blocks 1
#9
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
9
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa6b89ebb…a66e
0x34b655…2a6f
4 touches
1 conflict
0xf1d76dba…4de3
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x7c524e26…54c6
0x34b655…2a6f
4 touches
1 conflict
0x11401e68…c822
0x34b655…2a6f
2 touches
0 conflicts
0x32287d4a…6699
0x34b655…2a6f
2 touches
0 conflicts
0x87d58f4e…70c8
0x34b655…2a6f
2 touches
0 conflicts
0x99137b93…c390
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
0xa6b89ebbaf…5fa66e
Audit this contract →
← previous block
·
next block →
recent activity