pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,809,796
← previous block
next block →
recent activity
Analyzing
Block #94,809,796
9 transactions · 8 stateful · 2026-08-10 15:22:16 UTC
Parallelism
78
/100
Blocked
13
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,809,796
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrder
#2
execOrder
· blocks 1
#4
updateDataFeedsValuesPartial
#5
0x3f5c179b
#6
execFwdPositionOps
#7
batchUpdate
#8
forward
#3
execOrder
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb3fb9fb5…64db
0x34b655…2a6f
4 touches
1 conflict
0xa3a621f8…75a2
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x6676e87f…b88f
0x2a68ba…90c5
2 touches
0 conflicts
0x1c796c6b…064e
0x34b655…2a6f
2 touches
0 conflicts
0x1f620d34…475c
0x34b655…2a6f
2 touches
0 conflicts
0x2a1544ad…9f70
0x34b655…2a6f
2 touches
0 conflicts
0x47a10383…3e35
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
0xb3fb9fb561…7664db
Audit this contract →
← previous block
·
next block →
recent activity