pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,855,794
← previous block
next block →
recent activity
Analyzing
Block #94,855,794
11 transactions · 10 stateful · 2026-08-10 19:13:42 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,855,794
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5acec890
#2
execFwdPositionOps
#3
0xed82b078
#4
execFwdPositionOps
· blocks 1
#5
updateDataFeedsValuesPartial
#6
transferWithAuthorization
#7
0x6a7a235d
#8
setData
#9
withdraw
#10
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8ce1ffed…4889
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x85d4c7be…173a
0x34b655…2a6f
4 touches
1 conflict
0x098db796…75a4
0x34b655…2a6f
2 touches
0 conflicts
0x0dd7d6d8…3700
0x34b655…2a6f
2 touches
0 conflicts
0x28ceceef…ecc2
0x34b655…2a6f
2 touches
0 conflicts
0x3b9bb58c…e73a
0x34b655…2a6f
2 touches
0 conflicts
0x3c1a8ff6…a5a1
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
0x8ce1ffed3d…764889
Audit this contract →
← previous block
·
next block →
recent activity