pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,904,093
← previous block
next block →
recent activity
Analyzing
Block #94,904,093
10 transactions · 9 stateful · 2026-08-10 23:16:36 UTC
Parallelism
80
/100
Blocked
22
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,904,093
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execFwdPositionOps
· blocks 1
#3
placeAndExecuteMarketSell
#4
0x3f5c179b
#5
batchUpdate
#6
0x6a7a5c4c
#7
setData
#8
0x59558d29
· blocks 1
#2
execFwdPositionOps
#9
0x59558d29
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd30f9e74…d404
0x34b655…2a6f
4 touches
1 conflict
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x01a056f8…64e4
0x34b655…2a6f
2 touches
0 conflicts
0x044844a0…7418
0x34b655…2a6f
2 touches
0 conflicts
0x19795ad6…4a16
0x34b655…2a6f
2 touches
0 conflicts
0x1dfc34bb…34e9
0x34b655…2a6f
2 touches
0 conflicts
0x1dfc34bb…34ea
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
0xd30f9e74d6…9ed404
Audit this contract →
← previous block
·
next block →
recent activity