pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#91,404,545
← previous block
next block →
recent activity
Analyzing
Block #91,404,545
11 transactions · 11 stateful · 2026-07-29 17:34:14 UTC
Parallelism
73
/100
Blocked
18
%
Avg conflicts / tx
0.18
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#91,404,545
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
execPerpOps
#2
execFwdPositionOps
· blocks 1
#5
forward
#6
commit
#7
0x6a6a3a0e
#8
transfer
#9
setData
#10
0x59558d29
#3
execFwdPositionOps
· blocks 1
#4
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
4
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5af098c7…4807
0x34b655…2a6f
4 touches
1 conflict
0x5af098c7…4806
0x34b655…2a6f
4 touches
1 conflict
0xefcdf197…96a2
0x34b655…2a6f
4 touches
1 conflict
0x1a83fb77…7854
0x34b655…2a6f
2 touches
0 conflicts
0x279ddfdc…78fb
0x34b655…2a6f
2 touches
0 conflicts
0x279ddfdc…78fc
0x34b655…2a6f
2 touches
0 conflicts
0x39be1068…bbad
0x34b655…2a6f
2 touches
0 conflicts
0x41dc2b7f…1af1
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
0x5af098c77e…e94807
Audit this contract →
← previous block
·
next block →
recent activity