pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,973,587
← previous block
next block →
recent activity
Analyzing
Block #92,973,587
9 transactions · 8 stateful · 2026-08-04 05:09:09 UTC
Parallelism
67
/100
Blocked
25
%
Avg conflicts / tx
0.33
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,973,587
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
transfer
#2
updateDataFeedsValuesPartial
#3
executeBatch
#4
execFwdPositionOps
#5
execFwdPositionOps
#6
execOrders
· blocks 2
#7
execOrders
· blocks 1
#8
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
8
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x0f2d78b1…7363
0x34b655…2a6f
4 touches
1 conflict
0x8fa97406…a574
0x34b655…2a6f
4 touches
1 conflict
0xb79661b4…cbb4
0x754704…b603
2 touches
0 conflicts
0xc766cbf0…ef57
0x754704…b603
2 touches
0 conflicts
0x09e0690d…6e3d
0xe52b14…7230
2 touches
0 conflicts
0x17bbe4f8…08c5
0xe52b14…7230
2 touches
0 conflicts
0x28747f91…a9fd
0xe52b14…7230
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
3 conflicts on slot
0xd98b3c102b…ca67b8
Audit this contract →
← previous block
·
next block →
recent activity